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 --json before 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.
- Scan agents.
- Assess agents needing attention with
detail --tail 10.
- Act: approve, clarify, correct, delegate, relay, verify, or escalate.
- Report one brief status line.
- Sleep 10-60s and repeat.
Completion
Finish when all assigned work is verified, blocked with a clear reason, or stopped by the user. Summarize per-agent outcomes, verification, unresolved issues, and next step.
1---2name: agent-orchestration3description: AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.4---5
6# Agent Orchestration
7
8Use 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`.
9
10Use `$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.
11
12## Rules
13
14- Own the loop until assigned work is complete, blocked, or stopped.
15- Run `agent list --json` before each pass; never assume names/statuses.
16- Inspect waiting, idle, unknown, missing, or stale agents before acting.
17- Send self-contained instructions and avoid duplicate follow-ups.
18- Sequence agents that touch the same files; relay only relevant upstream output.
19- Escalate only for repeated failures, unresolved conflicts, product/business decisions, or destructive/shared/production/security-sensitive actions.
20
21## Loop
22
23If the goal or agent ownership is unclear, run one scan/detail pass. Ask the user once only if context is still insufficient.
24
251. Scan agents.
262. Assess agents needing attention with `detail --tail 10`.
273. Act: approve, clarify, correct, delegate, relay, verify, or escalate.
284. Report one brief status line.
295. Sleep 10-60s and repeat.
30
31## Completion
32
33Finish when all assigned work is verified, blocked with a clear reason, or stopped by the user. Summarize per-agent outcomes, verification, unresolved issues, and next step.
codeaholicguy