Multi-Agent Orchestrator
Use this skill when a task should run with a manager + specialist workflow instead of a single-agent change.
Trigger intent
- •
multi-agent-orchestrator <ISSUE-ID> - •
orchestrate <ISSUE-ID> - •
execute parent issue <ISSUE-ID>
If the input is an issue ID (for example DIM-14), treat it as the root orchestration issue.
Default operating contract
- •Follow nearest
AGENTS.mdanddocs/agent/*. - •If input is a root issue:
- •load parent issue details
- •discover child issues
- •load dependency edges (
blockedBy/blocks) - •build dependency waves (topological order)
- •execute same-wave issues in parallel when ownership is disjoint
- •gate each wave on reviewer/verifier checks
- •when running in GitHub Copilot CLI:
- •enable
/fleetfor same-wave parallel subagents - •use
/tasksto track and wait for subagent completion - •if
/fleetis unavailable, execute the same waves sequentially
- •enable
- •Use Linear parent/child issues as the primary orchestration record.
- •Only for exceptional high-risk/audit/incident cases, create a plan in
docs/agent/exec-plans/active/YYYYMMDD-<slug>.md. - •Decompose by file ownership:
- •client:
{{CLIENT_PATH}} - •server:
{{SERVER_PATH}} - •shared:
{{SHARED_PATH}}
- •client:
- •Assign mode per task:
delegate,review, orown. - •Run reviewer pass against:
- •
docs/agent/security.md - •
docs/agent/quality.md
- •
- •Run verifier checks and capture command evidence.
- •If formal plan was used, move plan to
docs/agent/exec-plans/completed/.