Standard Workflow

A clear methodology to ensure code quality and project consistency.

Technical Steps

Brainstorming

Initial step to align ideas and define the best approach before writing code.

Specification

Formal documentation of requirements, expected behavior, and acceptance criteria.

Phased Planning

Transforms the spec into small, reviewable, testable tasks (Implementation Plan).

TDD Cycle

Red → Green → Refactor. Write the test first, then the minimal code to pass.

Automated Review

Verification with subagents and linters before committing any changes.

Systematic Debugging

Structured debugging with hypotheses, investigation, and systematic verification.

Finishing a Development Branch

Cleanup and preparation for merge. Clean commits, PR ready for review.

SDD in Practice

The official Superpowers flow is skill-driven. You mostly describe intent, approve design, and start execution.

1. Brainstorming

Describe the problem; the skill should activate automatically

How to use

I want to add JWT authentication
with refresh tokens and revocation.

Expected skill:
brainstorming

Output

Design discussion

Requirements, trade-offs, and architecture are refined conversationally.

Design file

Saved under docs/superpowers/specs/ after approval.

2. Worktree + Plan

After approval, Superpowers isolates the work and writes the implementation plan

Expected skills

using-git-worktrees
writing-plans

Output

docs/superpowers/specs/...-design.md
docs/superpowers/plans/...md

The plan breaks work into small,
testable tasks with explicit verification.

3. Execution + TDD

Run the approved plan task by task

Recommended execution

/subagent-driven-development

Alternative:
executing-plans

TDD inside each task

RED

Write the failing test first.

GREEN

Write the minimum code to pass.

REFACTOR

Improve structure without breaking tests.

4. Review Between Tasks

Review is part of the workflow, not an afterthought

Expected skill

requesting-code-review

What it checks

Plan compliance

Verifies the implementation still matches the approved design and plan.

Quality issues

Flags non-blocking concerns for cleanup.

Critical blockers

Stops progress when the task introduces serious defects.

6. Systematic Debugging

Hypothesis → Investigation → Surgical fix

How to use

/debug-issue

Describe the symptom:
"Refresh token returns 401
after 30 minutes"

The AI follows the method:
1. Formulates hypotheses
2. Investigates each one
3. Applies surgical fix
4. Verifies with tests

Method

1. Hypothesis

"Token expired? Clock skew? Wrong secret?"

2. Investigation

Checks logs, tests each hypothesis in isolation.

3. Fix

Applies minimal fix. No refactoring during debug.

7. Finish the Branch

Close out with the official finishing workflow

How to finalize

/finishing-a-development-branch

Typical outcomes:
- merge now
- open a PR
- keep the branch
- discard the branch

Final Checklist

✓ All tests pass

✓ Reviews are resolved

✓ Branch state is explicit

✓ Verification ran before completion

✓ Merge or PR decision is documented

Memory System

4 layers of memory, each with clear responsibility. Context that survives between sessions.

Layer	Scope	Persistence	Status
Rules	Project conventions and patterns	Committed to repo	commitado
Learnings	Decisions and lessons from sessions	Committed to repo	commitado
Sessions	Current conversation context	Ephemeral (conversation)	automático
Auto Dream	Learned entities and preferences	Semantic memory (MCP)	mem0

Next Step

Understand the structure generated by the wizard and how each piece connects.

View Structure