| name | dispatch-agents |
| description | Use when you have 2+ independent tasks with no shared state — dispatches parallel subagents for each task. |
Dispatching Parallel Agents
When to Use
- Tasks are truly independent (no shared files, no sequential dependency)
- Each task is well-defined with clear success criteria
- 2-5 tasks in parallel (more than 5 becomes hard to review)
Process
- List all tasks and confirm independence
- For each task, write a self-contained prompt including:
- Full context (don't assume agent knows anything)
- Exact files to touch
- Success criteria
- How to verify
- Dispatch all agents simultaneously using the Agent tool
- Collect results and merge
- Run verification across all changes together
- Invoke
requesting-code-review to dispatch the code-reviewer agent on merged result, then handle findings via receiving-code-review
Safety
Never dispatch agents for tasks involving shared state — race conditions and conflicts will waste more time than sequential execution saves.