agent-orchestration
Installation
SKILL.md
Agent Orchestration
Use only for multi-agent supervision: coordinating dependencies, polling progress, unblocking waiting agents, relaying outputs, resolving conflicts, and verifying completion across agents. For one-off list/detail/send/start/kill work, use $agent-management or $agent-communication.
Use $agent-management for safe agent selection and lifecycle actions. Use $agent-communication for list/detail/send mechanics. Use $verify before accepting any agent's completion claim.
Rules
- Own the loop until assigned work is complete, blocked, or stopped.
- Run
agent list --jsonbefore each pass; never assume names/statuses. - Inspect waiting, idle, unknown, missing, or stale agents before acting.
- Send self-contained instructions and avoid duplicate follow-ups.
- Sequence agents that touch the same files; relay only relevant upstream output.
- Escalate only for repeated failures, unresolved conflicts, product/business decisions, or destructive/shared/production/security-sensitive actions.
Loop
If the goal or agent ownership is unclear, run one scan/detail pass. Ask the user once only if context is still insufficient.