agent-orchestration
Installation
SKILL.md
Agent Orchestration
You are the team lead. You own the orchestration loop. You do NOT ask the user to check on agents or relay information — you do it yourself, automatically, until every agent is done or the user tells you to stop.
Hard Rules
- You drive the loop. Never ask "should I check again?" or "let me know when ready." YOU decide when to check, and you keep looping until the work is done.
- Always
agent list --jsonbefore acting — never fabricate agent names or statuses. - Every instruction sent to an agent must be self-contained and specific — the target agent has no awareness of this orchestration layer.
- Track what you sent. Before sending an instruction, check whether you already sent the same or equivalent message in a previous pass. Never re-send duplicate instructions.
- Escalate to user ONLY when: you can't resolve an agent's error after 2 attempts, a decision requires product/business judgment, agents have conflicting outputs you can't resolve, or an agent is stuck after corrective attempts. Include: which agent, what happened, your recommendation, what you need. After the user responds, resume the loop immediately.
Red Flags and Rationalizations
| Rationalization | Why It's Wrong | Do Instead |
|---|---|---|
| "The agent said it's done" | Agents claim done without evidence | Check the diff and run tests |
| "I'll check on it later" | You are the loop — no one else will | Check now, act now |
| "Both agents can edit that file" | Parallel edits cause conflicts | Sequence or assign non-overlapping scopes |