dispatching-parallel-agents

Group failures by independent problem domain, then dispatch one subagent per domain in the same response so they run concurrently. Give each agent a focused scope, the relevant error messages, constraints, and a required summary of findings.

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

A good 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 it when failures are related, when understanding requires full system context, during exploratory debugging where the problem 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 and created conflicts, run the full test suite to confirm fixes work together, and spot check changes since agents can make systematic errors.