multi-agent-orchestration

quick workflow

1. **Detect** — Is this task parallelizable? Check overlap. If files overlap → sequential. 2. **Decompose** — Break into non-overlapping sub-tasks. Plan context per subagent. 3. **Delegate** — Launch subagents via task tool. Pass only relevant skill + context. 4. **Collect** — Receive results. Verify each subagent's output independently. 5. **Integrate** — Merge files. Resolve conflicts. Run build/tests. 6. **Verify** — Full integration test. Only Orchestrator commits.
---

load order

1. This SKILL.md (index) 2. GUIDE.md — Full patterns, real examples, error recovery 3. If parallelizing: reference target skill per subagent (frontend-web`, `backend-api-mastery, etc.)
---

relation to other skills

| This skill | Other skill | Why | |---|---|---| | Orchestrator delegates build | incremental-implementation | Subagent 1 builds module A | | Orchestrator delegates tests | test-driven-development | Subagent 2 writes tests | | Orchestrator delegates review | code-review-and-quality | Subagent 3 reviews output |
---

red flags

• Subagents editing the same file simultaneously
• Subagents receiving full AGENTS.md
• Orchestrator commits without verifying subagent output
• explore agent type used for writing code (read-only!)
• No error handling when subagent fails

---


verification



• [ ] Sub-tasks have non-overlapping file assignments
• [ ] Each subagent receives only its relevant skill
• [ ] Subagent output verified before integration
• [ ] Orchestrator merges, tests, then commits (never subagents)
• [ ] Build + tests pass after integration