dispatching-parallel-agents
Dispatching Parallel Agents
When to Use
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 (editing same files, using same resources)
- Exploratory debugging (you don't know what's broken yet)
The Pattern
1. Identify Independent Domains
More from schlenks/superpowers-bd
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
10writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
9brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
8epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
8rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
8systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8