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, constraints, and expected output. After agents return, review summaries, check for conflicts, and run the full test suite.

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, or agents would edit the same files, investigate sequentially instead.

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

Avoid parallel dispatch when failures are related, when understanding requires full system context, during exploratory debugging where the problem is unknown, or when agents would interfere through shared state like editing the same files.

Read each agent's summary to understand what changed, 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.