dispatching-parallel-agents

Topics in the source

• Dispatching Parallel Agents
• Overview
• When to Use
• The Pattern
• 1. Identify Independent Domains
• 2. Create Focused Agent Tasks
• 3. Dispatch in Parallel
• 4. Review and Integrate

When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel. Core principle: Dispatch one agent per independent problem domain. Let them work concurrently. Use when: 3+ test files failing with different root causes Multiple subsystems broken independently Each problem can be understood without context from others No shared state between investigations Don't use when: Failures are related (fix one might fix others) Need to understand full system state Agents would interfere with each other Group failures by what's broken: File A tests: Tool approval flow File B tests: Batch completion behavior File C tests: Abort functionality Each domain is independent - fixing tool approval doesn't affect abort tests. Each agent gets: Specific scope: One test file or subsystem Clear goal: Make these tests pass Constraints: Don't change other code Expected output: Summary of what you found and fixed When agents return: Read each summary Verify fixes don't conflict Run full test suite Integrate all changes Good agent prompts are: 1. Focused - One clear

This is an excerpt. Refer to the complete source and its current requirements.