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. After agents return, review each summary, check for conflicting edits, and run the full test suite.

Use parallel agents when failures are independent—different root causes, different files, no shared state—and each can be understood without context from the others. If fixing one failure might fix others, investigate them together first.

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 changes.

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 or resources.

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.