What problem does it solve?
Decompose complex tasks into independent, parallel sub-agents with no overlapping concerns, race conditions, or inter-agent dependencies. Use BEFORE spawning Task agents when the work involves multiple files, domains, or concerns that could be parallelized. Triggers on: planning multi-agent work, "split this into agents", "parallelize this", "divide and conquer", or when about to launch 2+ Task agents for a complex task. Also use when a task feels too large for a single agent but the right decomposition isn't obvious.
Core Features & Use Cases
- Formalized process to identify boundaries and ensure independence between agents.
- Guidance on safe split patterns and conflict checks to prevent write collisions.
- Practical workflow for launching parallel agents with minimal coordination.
Quick Start
Outline a 2- to 5-agent decomposition for a given complex task, assign each agent a distinct concern, and specify their write boundaries to ensure conflict-free parallel execution.