dispatching-parallel-agents

Group failures by independent problem domain, then dispatch one agent per domain with a focused prompt containing the error messages, scope, and constraints. Each agent investigates concurrently, and you review and integrate their summaries afterward.

Use parallel dispatch when failures are independent, such as different test files or subsystems with 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 pasted 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.

Yes, if their scopes overlap or they edit shared files. Prevent this by assigning strictly independent domains, then after agents return, review each summary, check for conflicting edits, and run the full test suite to verify integration.

Avoid it 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.