parallel-agents
Dispatching Parallel Agents
Overview
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. Each agent gets its own planning directory for structured knowledge capture.
Core principle: Dispatch one agent per independent problem domain with its own planning dir. 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];
"Sequential agents" [shape=box];
"Parallel dispatch" [shape=box];
More from sipengxie2024/superpower-planning
brainstorming
Use when designing complex multi-step features, building new components, or planning significant behavior changes that require design exploration before implementation.
10main
Skill router and planning initialization. Loaded on every session start. Determines which skills to invoke and ensures .planning/ is initialized for complex tasks.
9subagent-driven
Use when executing implementation plans with independent tasks in the current session
9debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8planning-foundation
Implements persistent file-based planning for complex tasks. Creates .planning/ directory with progress.md and findings.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Foundation layer inherited by all other skills.
8tdd
Use when implementing any feature or bugfix, before writing implementation code
7