Superpowers Quick‑Start Guide: A Structured Workflow to Make AI‑Generated Code Reliable

What is Superpowers?

Superpowers is a fixed workflow for AI coding tools (Claude Code / OpenCode) that structures code generation into three commands: brainstorm, write‑plan, execute‑plan.

Git repository: https://github.com/obra/superpowers

Core philosophy

Design‑driven → Plan‑driven → Test‑driven → Quality‑driven

Test‑Driven Development (TDD) – write tests first.

Systematic over ad‑hoc – follow a process.

Complexity reduction – keep solutions simple.

Evidence over assertion – verify before claiming success.

When to use Superpowers

Feature development where requirements are unclear (e.g., adding dark mode or a search box).

Concern that AI may modify code arbitrarily.

Need for maintainable code without hidden pitfalls.

Not needed for simple copy edits, typo fixes, or one‑off scripts.

Preparation

Claude Code (recommended)

Open the Claude Code terminal.

Run the plugin commands:

/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace

Verify commands are available with /help. Expected commands:

/superpowers:brainstorm
/superpowers:write-plan
/superpowers:execute-plan

OpenCode (simple method)

In OpenCode settings add the following instruction:

From https://github.com/obra/superpowers learn how to use Superpowers.
When I mention "use Superpowers workflow", follow this order:
1) brainstorm
2) write‑plan
3) execute‑plan

Three core steps

brainstorm – Clarify the desired feature.

write‑plan – Generate a human‑readable implementation plan.

execute‑plan – Apply the plan step‑by‑step, with the AI reporting changed files and test instructions after each step.

Step 1: brainstorm

Run /superpowers:brainstorm. The AI will:

Ask step‑by‑step questions to pinpoint the feature.

Confirm goals, constraints, and success criteria.

Provide 2–3 implementation ideas and help select one.

Step 2: write‑plan

After brainstorming, run /superpowers:write-plan (or ask “Help me write an implementation plan using Superpowers”). A typical plan includes:

Files to modify or add.

Specific actions for each step.

Verification commands and expected results.

Each step is intended to take 2–5 minutes and be understandable by any developer.

Step 3: execute‑plan

Run /superpowers:execute-plan with a prompt such as “Follow this plan step by step; after each step show me what changed.” After each step the AI reports:

Which files were changed.

Why the change was made.

Prompt to run tests or view the result.

Worked example: dark‑mode toggle

Goal: add a dark‑mode switch button to a website with the following behavior:

Default light theme.

Button toggles between light and dark.

Choice persists across page reloads.

Workflow:

Issue /superpowers:brainstorm. AI asks about front‑end framework, browser compatibility, and scope of style changes.

Issue /superpowers:write-plan. Example plan:

Add a “toggle theme” button to the page.

Store the current theme in a variable.

On button click, switch the theme and update styles.

Persist the theme in localStorage.

On page load, read localStorage and apply the saved theme.

Issue /superpowers:execute-plan with a prompt to stop after each step. After each step, run the project locally to verify the UI and test the persisted theme.

Typical daily usage

Adopt Superpowers as a collaboration convention:

Declare “All upcoming tasks use Superpowers: brainstorm → write‑plan → execute‑plan.”

For each new feature:

Use brainstorm to clarify requirements.

Use write‑plan to produce a TODO‑style plan.

Use execute‑plan to implement and test step‑by‑step.

When time is limited:

Small feature: brainstorm + simple plan.

Medium feature: brainstorm + plan + manual implementation.

Large feature: full three‑step workflow.

Common questions

Do I need to remember all commands?

Only the principle matters: let the AI clarify before coding. If a command is forgotten, instruct the AI to “use Superpowers workflow” and it will select appropriate steps.

Is the workflow slower?

Initial overhead is slightly higher than direct AI edits, but it yields features that match requirements, easier error localisation, and more maintainable code.

Can I use only part of the workflow?

Yes. Use brainstorm alone to clarify needs, add write‑plan for a structured plan, or use the full set for formal development.