Properties2
| Type | Practice |
| Note created | Apr 8, 2026 |
The Superpowers plugin for Claude Code enforces a disciplined development workflow: brainstorm → plan → implement → review → finish. These are the steps to follow, in order.
Workflow Steps
- Brainstorming (
/brainstorming) — Explore the problem via Socratic dialogue. Refine requirements before any code is written. Never skip this, even for simple tasks. - Writing Plans (
/writing-plans) — Break the approved design into granular tasks (2-5 min each) with exact file paths, runnable code, and verification commands. No placeholders allowed. - Git Worktree (
/using-git-worktrees) — Create an isolated branch and workspace. Verify a clean test baseline before starting. - Execution — Pick one mode depending on the situation:
/executing-plans— Batch execution with human checkpoints between phases./subagent-driven-development— Fresh subagent per task with two-stage review (spec compliance, then code quality)./dispatching-parallel-agents— For 3+ truly independent tasks.
- Test-Driven Development (
/test-driven-development) — Active throughout implementation. Red → Green → Refactor. Code written before tests gets deleted. - Code Review (
/requesting-code-review) — Verify work against the plan. Critical issues block progress. - Verification (
/verification-before-completion) — Run verification commands and confirm output before claiming anything is done. - Finishing (
/finishing-a-development-branch) — Choose: merge locally, push and create PR, keep branch, or discard.
Reactive Skills
These trigger when needed, not at a fixed step:
- Systematic Debugging (
/systematic-debugging) — 4-phase root cause analysis. After 3 failed fixes, stop and question the architecture. - Receiving Code Review (
/receiving-code-review) — When processing feedback from others. Requires verification, not blind agreement.
Key Rules
- The only valid exit from brainstorming is writing plans — never jump to code.
- Never claim “done” without running verification-before-completion.
- Plans are markdown files in the repo — edit them directly in any editor.
- User instructions always override skill behavior.