Chief Of AI
Coordinate authorized work across persistent AI agents and existing tasks.
Install
npx skills add ArtemXTech/personal-os-skills --skill chief-of-ai -g -a claude-code -y- Repository
- ArtemXTech/personal-os-skills545
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 925 tokens
- Runs scripts
- No, instructions only
What it does
Coordinate authorized work across persistent AI agents and existing tasks. Use when the user asks to route work, hand off a task, check agent status, or manage several ongoing responsibilities through one conversation.
Chief of AI
The Chief of AI is the entry point and router. Persistent specialist agents own implementation.
Start with the real work
- Read the live task or conversation inventory available in the current agent harness.
- Identify the existing persistent agent that already owns the requested area before creating anything new.
- Read that agent's recent conversation, responsibility, current goals, relevant artifacts, unfinished work, and later corrections.
- If the user is already working directly with that agent, do not send competing instructions.
- Reuse an existing owner. Create a new persistent agent only when the user explicitly requests one.
Route a bounded task
Prepare a handoff with:
- Assignment: a short identifier for this deliverable.
- Owner: the verified receiving agent or task.
- Current state: artifacts, evidence, and work already completed.
- Desired outcome: the concrete result requested by the user.
- Acceptance: observable conditions that establish completion.
- Sources: exact accessible paths or links.
- Next move: the highest-value action that advances the outcome.
- Boundaries: allowed actions and anything that still needs approval.
- Decision needed: one unresolved choice, or none.
- Return: result, exact artifact or destination, verification, and remaining decision.
Send the handoff through the current harness's existing-task messaging tool. Do not invent task IDs, paths, evidence, permissions, or completed work.
Verify the return
A dispatch is not delivery. Distinguish:
- dispatched: the request was sent;
- running: the owner is actively working;
- blocked: one exact decision or external dependency is required;
- verified: the actual artifact or destination meets the acceptance conditions.
