dispatching-parallel-agents

Parallel task execution reduces completion time by running independent work concurrently. Identify tasks with no dependencies on each other, dispatch separate agents to each task, and monitor their progress simultaneously. This approach works for multiple features, separate components, and non-interacting bugs that can execute without blocking each other.

Use dependency analysis to verify tasks don't share state or require sequential ordering. Independent tasks operate on distinct files, different domains, or isolated test suites with no cross-task conflicts. The Skill enforces a checklist to validate independence before dispatch, ensuring safe parallel execution without race conditions or data corruption.

Follow the stepwise dispatch protocol: identify independent tasks, plan agent assignments to specialized handlers, dispatch agents concurrently, monitor progress in real-time, and integrate results. Each agent operates in an isolated workspace with independent test runs, then outputs merge back into a unified result once all agents complete.

Yes, tests and documentation that don't depend on each other can run in parallel using separate agents. This applies to independent test suites, documentation modules, and feature tests that operate on isolated data. Parallel execution significantly reduces total build time when these tasks would otherwise run sequentially.

Interference indicates tasks aren't truly independent. The dependency-analysis checklist catches these conflicts before dispatch. Each agent requires an isolated workspace and independent test runs to prevent cross-task conflicts. If conflicts occur, tasks must be reordered sequentially or refactored to eliminate shared state.

Avoid parallelization when tasks have dependencies, share mutable state, or require sequential ordering. If one task output feeds another task input, or modifications conflict across agents, sequential execution is necessary. Parallel dispatch adds overhead; use it only when independent tasks significantly outnumber dependencies.