Superpowers

Disciplined, systematic approach to AI-assisted software development. 13 integrated skills covering the full development lifecycle.

The 7-Step Workflow

1. Brainstorm — Design before implementation (Section 2)
2. Plan — Write detailed implementation plan (Section 3)
3. Execute — Implement with subagents or batches (Sections 4-6)
4. Test — TDD throughout: RED-GREEN-REFACTOR (Section 7)
5. Debug — Systematic root cause analysis when needed (Section 8)
6. Review — Code review after each task (Section 10)
7. Finish — Branch completion and integration (Section 12)

How to Use

Apply the relevant section based on your current task:

Task	Section
Starting new work	Section 2 (Brainstorming) → Section 3 (Writing Plans)
Implementing a plan (this session)	Section 5 (Subagent-Driven Development)
Implementing a plan (separate session)	Section 4 (Executing Plans)
Multiple independent problems	Section 6 (Dispatching Parallel Agents)
Writing or fixing code	Section 7 (Test-Driven Development)
Bug, test failure, unexpected behavior	Section 8 (Systematic Debugging)
About to claim work is done	Section 9 (Verification Before Completion)
After completing work	Section 10 (Code Review)
Need isolated workspace	Section 11 (Using Git Worktrees)
Ready to merge/integrate	Section 12 (Finishing a Development Branch)
Creating new skills	Section 13 (Writing Skills)

Skill priority: Process skills first (brainstorming, debugging), then implementation skills.

Skill types:

• Rigid (TDD, debugging, verification): Follow exactly. Don't adapt away discipline.
• Flexible (patterns, worktrees): Adapt principles to context.

---

1. Using Superpowers

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>

Rule: Invoke relevant skills BEFORE any response or action. Even a 1% chance a section might apply means you should check.

Process:

1. User message received
2. Check: might any section apply?
   • Yes → Follow that section
   • No → Respond directly
3. If about to plan: check Section 2 (Brainstorming) first
4. If section has checklist: create todo per checklist item
5. Announce: "Using [skill] to [purpose]"

Priority order:

1. Process sections first (brainstorming, debugging)
2. Implementation sections second

User instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.

Red Flags — You're Rationalizing