Home/Skills/dev/Dispatching Parallel Agents

/dispatching-parallel-agents

Dispatching Parallel Agents

Three independent failures. One sequential debug. That math is wrong. Dispatch in parallel.

Used by 1 agent

What it does

Routes independent problems to focused subagents running concurrently. Each agent gets narrow scope, clear goal, explicit constraints, and a required output shape. Your own context stays lean for coordination instead of drowning in per-task detail.

Use it when 3+ test files fail for different reasons, when multiple subsystems break independently, or when a plan has parallel workstreams with no shared state. Don't use it when failures are related, when exploratory debugging is still active, or when agents would edit the same files.

Outputs a dispatch plan with one agent per domain, then integrates their returns: read each summary, check for conflicts, run the full suite. Pairs with `subagent-driven-development` (the broader pattern) and `executing-plans` (when the plan itself is the parallelization source).

Build your second brain

Run /dispatching-parallel-agents with your agents.

This skill ships with Agent0 Starter, plus 82 others. Axon runs it from day one.

Cortex
Chief of Staff
Loom
Loom
Radar
Radar
Hippo
Hippocampus
Signal
Signal
Sentinel
Sentinel
Axon
Axon
Hey, I'm Cortex — Chief of Staff for the team. Ask me anything; I'll handle it or pull in Loom (writing), Radar (growth), Hippocampus (research), Signal (social), Sentinel (ops), or Axon (code review). What's on your mind?