dispatching-parallel-agents
Delegate independent tasks to specialized agents working concurrently with isolated context.
- Dispatch one agent per problem domain when facing 3+ unrelated failures across different test files or subsystems
- Each agent receives focused scope, clear goal, and constraints—no inherited session context or history
- Agents work in parallel on independent investigations, then you review summaries and integrate non-conflicting fixes
- Best for timing issues, subsystem bugs, and exploratory fixes where root causes are unrelated; avoid when failures are connected or require shared state
Dispatching Parallel Agents
Overview
You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
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.
When to Use
digraph when_to_use {
"Multiple failures?" [shape=diamond];
"Are they independent?" [shape=diamond];
"Single agent investigates all" [shape=box];
"One agent per problem domain" [shape=box];
"Can they work in parallel?" [shape=diamond];
More from obra/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
152.3Kusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
92.7Ksystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
92.0Kwriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
91.3Krequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
80.4Ktest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
79.8K
More in Agent workflows
find-skills
Discover and install skills from skills.sh directly inside an agent session
vercel-labs/skillsagent-browser
Full browser automation: navigate, click, fill forms, extract data, and screenshot
vercel-labs/agent-browserskill-creator
Create, test, and publish new skills from within your agent
anthropics/skillsbrowser-use
Browser automation with visual understanding — interacts with pages based on what it sees
browser-use/browser-useexecuting-plans
Execute a plan step-by-step with checkpoints and verification at each stage
obra/superpowers