dispatching-parallel-agents
Installation
SKILL.md
Dispatching Parallel Agents
Effective orchestration means knowing when to do work yourself and when to delegate it to focused subagents working in parallel. The core insight is simple: independent work should happen concurrently, not sequentially. But "independent" is the load-bearing word -- getting decomposition wrong turns parallel execution into a coordination nightmare.
Core Principles
| Principle | Meaning |
|---|---|
| Independence over coordination | If two tasks share state, they are one task. Only dispatch work that can complete without cross-agent communication. |
| Precision over hope | A subagent brief must be specific enough that the agent cannot misinterpret its scope. Vague briefs produce vague results. |
| Isolation over sharing | Each subagent starts with a clean context. It receives exactly what it needs -- nothing inherited, nothing ambient. |
| Synthesis over concatenation | The orchestrator's job is not to paste outputs together. It is to resolve conflicts, deduplicate, and produce a coherent whole. |
| Fail fast over fail silent | Every dispatch includes a failure mode. Subagents report blockers immediately rather than guessing past them. |