◈  Superpowers
01 / 08
← → space
Superpowers // Claude Code

The Basic
Workflow

A systematic approach to AI-assisted development.
Mandatory workflows, not suggestions.
Brainstorming Git Worktrees Writing Plans Subagent Dev Test-Driven Dev Code Review Finishing the Branch COMPLEXITY REDUCTION The first three phases share one goal: eliminate ambiguity before code exists. Confusion deferred is debt compounded. SYSTEMATIC OVER AD-HOC Each phase has a defined trigger and output. The workflow never improvises between steps. Process is the architecture. TEST-DRIVEN DEVELOPMENT Writing the test first isn't a ritual. It's the only honest way to know what "done" means before you claim it. EVIDENCE OVER CLAIMS Critical issues block progress. The system trusts verified outcomes — never the intent behind them. Ship means ship.
01 // Brainstorming

Refine Before
You Code

Activates before writing code. Refines rough ideas through questions, explores alternatives, and validates the design in sections.

Questions over assumptions
Alternatives explored, not just the first idea
Design document saved for the next phase
02 // Git Worktrees

Isolated
Workspace

Activates after design approval. Creates an isolated workspace on a new branch, runs project setup, and verifies a clean test baseline.

Changes don't bleed into main
Project setup reproduced from scratch
Clean baseline locked in before writing any code
03 // Writing Plans

Break It
Down

Activates with the approved design. Breaks work into 2–5 minute tasks, each with exact file paths, complete code, and a verification step.

Tasks small enough to avoid context drift
Exact file paths — no ambiguity
Verification step baked into every task
04 // Subagent-Driven Dev

Parallel
Execution

Activates with the plan. Dispatches a fresh subagent per task with two-stage review, or runs in batches with human checkpoints.

Fresh context per task — no accumulated drift
Two-stage review: spec compliance → code quality
Human checkpoint between batches
05 // Test-Driven Development

Red → Green
→ Refactor

Activates during implementation. Write a failing test, watch it fail, write minimal code to pass, then commit. Code written before tests is deleted.

Red
→
Green
→
Refactor
06 // Code Review

Validate at
Every Step

Activates between tasks. Reviews against the plan and reports issues by severity. Critical issues block progress.

Spec compliance checked before code quality
Issues triaged: critical vs. advisory
Critical issues are hard blockers
07 // Finishing the Branch

Ship With
Confidence

Activates when all tasks are complete. Verifies the full test suite passes, presents your options, then cleans up the worktree.

Merge
Open PR
Keep
Discard