Subagent-Driven Development

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.

Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration

When to Use

vs. Executing Plans (parallel session):

• •Same session (no context switch)
• •Fresh subagent per task (no context pollution)
• •Two-stage review after each task: spec compliance first, then code quality
• •Faster iteration (no human-in-loop between tasks)

The Process

1. •Setup: Read plan, extract all tasks with full text, note context, create TodoWrite.
2. •Execute Loop (Per Task): a. Dispatch implementer (use ./implementer-prompt.md) b. Answer questions if implementer asks c. Implementer works: implements, tests, commits, self-reviews d. Dispatch spec reviewer (use ./spec-reviewer-prompt.md) e. Fix spec gaps if issues found -> Re-review f. Dispatch code quality reviewer (use ./code-quality-reviewer-prompt.md) g. Fix quality issues if found -> Re-review h. Mark complete in TodoWrite
3. •Finish: When all tasks done, dispatch final code reviewer, then use finishing-a-development-branch.

Prompt Templates

• •./implementer-prompt.md - Dispatch implementer subagent
• •./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent
• •./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagent

Example Workflow

You: I'm using Subagent-Driven Development to execute this plan.

[Read plan file once: docs/plans/feature-plan.md]
[Extract all 5 tasks with full text and context]
[Create TodoWrite with all tasks]

Task 1: Hook installation script

[Get Task 1 text and context (already extracted)]
[Dispatch implementation subagent with full task text + context]

Implementer: "Before I begin - should the hook be installed at user or system level?"

You: "User level (~/.config/superpowers/hooks/)"

Implementer: "Got it. Implementing now..."
[Later] Implementer:
  - Implemented install-hook command
  - Added tests, 5/5 passing
  - Self-review: Found I missed --force flag, added it
  - Committed

[Dispatch spec compliance reviewer]
Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra

[Get git SHAs, dispatch code quality reviewer]
Code reviewer: Strengths: Good test coverage, clean. Issues: None. Approved.

[Mark Task 1 complete]
...

Advantages

vs. Manual execution:

• •Subagents follow TDD naturally
• •Fresh context per task (no confusion)
• •Parallel-safe (subagents don't interfere)
• •Subagent can ask questions (before AND during work)

vs. Executing Plans:

• •Same session (no handoff)
• •Continuous progress (no waiting)
• •Review checkpoints automatic

Efficiency gains:

• •No file reading overhead (controller provides full text)
• •Controller curates exactly what context is needed
• •Subagent gets complete information upfront
• •Questions surfaced before work begins (not after)

Quality gates:

• •Self-review catches issues before handoff
• •Two-stage review: spec compliance, then code quality
• •Review loops ensure fixes actually work
• •Spec compliance prevents over/under-building
• •Code quality ensures implementation is well-built

Red Flags

Never:

• •Skip reviews (spec compliance OR code quality)
• •Proceed with unfixed issues
• •Dispatch multiple implementation subagents in parallel (conflicts)
• •Make subagent read plan file (provide full text instead)
• •Skip scene-setting context (subagent needs to understand where task fits)
• •Ignore subagent questions (answer before letting them proceed)
• •Accept "close enough" on spec compliance (spec reviewer found issues = not done)
• •Skip review loops (reviewer found issues = implementer fixes = review again)
• •Let implementer self-review replace actual review (both are needed)
• •Start code quality review before spec compliance is ✅ (wrong order)
• •Move to next task while either review has open issues

If subagent asks questions:

• •Answer clearly and completely
• •Provide additional context if needed
• •Don't rush them into implementation

If reviewer finds issues:

• •Implementer (same subagent) fixes them
• •Reviewer reviews again
• •Repeat until approved
• •Don't skip the re-review

Integration

Required workflow skills:

• •planning - Creates the plan this skill executes
• •requesting-code-review - Code review template for reviewer subagents
• •finishing-a-development-branch - Complete development after all tasks

Subagents should use:

• •test-driven-development - Subagents follow TDD for each task

Alternative workflow:

• •executing-plans - Use for parallel session instead of same-session execution