dispatching-parallel-agents

Group failures by independent problem domain, then dispatch one agent per domain with a focused prompt containing the failing test names, error messages, and constraints. Each agent works concurrently with isolated context, and you integrate their fixes afterward.

Use parallel dispatch when failures are independent, such as different test files or subsystems with different root causes and no shared state. If fixing one failure might fix others, investigate them together first instead.

A good agent prompt is focused on one problem domain, self-contained with pasted error messages and test names, explicit about constraints like not changing production code, and specific about the expected output such as a summary of root cause and fixes.

Avoid parallel dispatch when failures are related, when understanding requires full system context, during exploratory debugging where the cause is unknown, or when agents would share state such as editing the same files.

Read each agent's summary, check whether agents edited the same code, run the full test suite to confirm all fixes work together, and spot check results since agents can make systematic errors.