Parallel Dispatch Skill

Philosophy

Parallel dispatch is not "fire and forget" — it is "fire, verify, and integrate." The value of parallelism comes from independent execution, but the risk comes from unverified output. Every agent is treated as an untrusted contractor: given a clear scope, expected to deliver, but verified independently before their work is accepted. The dispatch orchestrator's primary job is not delegation — it is verification.

When to Use

• When 2+ independent tracks can execute concurrently without file conflicts
• For multi-module fixes, refactors, or feature additions across a workspace
• When time pressure demands parallel execution over sequential safety
• For commission-style work where each track has clear boundaries

Workflow