dispatching-parallel-agents

Group failures by independent problem domain, then dispatch one agent per domain with a focused prompt covering scope, constraints, and expected output. After agents return, review summaries, check for conflicts, and run the full test suite.

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

Avoid parallel dispatch when failures are related and fixing one might fix others, when understanding requires full system context, during exploratory debugging, 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.

Agents working concurrently interfere when they edit the same files or use the same resources, causing conflicting changes. Parallel dispatch only works when each problem domain is fully independent.