
Subagent Driven Development
Here's a workflow for executing implementation plans by dispatching fresh Claude instances per task, then running two-stage reviews on each result. You extract all tasks from your plan, dispatch an implementer subagent with isolated context, then run spec compliance and code quality reviews before moving to the next task. The key insight is using fresh context per task to avoid pollution while staying in your current session for coordination. Works well when you have independent tasks that don't need tight coupling. Includes prompt templates for implementer, spec reviewer, and quality reviewer roles, plus logic for handling different completion statuses and selecting appropriate model tiers based on task complexity.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 31
- skills.sh installs
- 252K
- GitHub stars
- 315.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add obra/superpowers --skill subagent-driven-development --agent claude-codeInstalls into .claude/skills of the current project.
Files
Subagent-Driven Development
Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the end.
Why subagents: 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.
Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration
Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record.
Continuous execution: Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are the four named below, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time — they asked you to execute the plan, so execute it.
Sponsors
Details
- Repository
- github.com/obra/superpowers
- Category
- AI & Agent Building
More from obra/superpowers
All 14- Receiving Code Review235.1K
- Dispatching Parallel Agents231.3K
- Writing Skills231.3K
- Using Git Worktrees230.2K
- Finishing A Development Branch227.7K
- Brainstorming423.3K
- Systematic Debugging326.7K
- Writing Plans298.6K
- Using Superpowers283.7K
- Requesting Code Review276.5K
- Test Driven Development274.8K
- Verification Before Completion270.3K
- Executing Plans257.5K