superpowers-workflowlisted

# Superpowers Workflow Skill ## Purpose Run non-trivial engineering work through a structured sequence — brainstorm, plan, test-drive, execute, verify, review — instead of ad-hoc code generation. ## When to use Use this skill for multi-file features, refactors, migrations, and hard debugging. Skip it for one-line fixes; the ceremony costs more than it returns there. ## Inputs - the feature or change request - affected surface area of the codebase - existing test setup and CI - definition of done ## Output Return, in order: 1. **Brainstorming** — the approaches considered and the one chosen, with the reason 2. **A written plan** — files to touch, interfaces to change, risks, and what is out of scope 3. **Failing tests** that encode the requirement 4. **The implementation** that makes them pass 5. **Verification before completion** — the commands actually run and their output 6. **Code review** — an adversarial pass against the plan, and what it changed ## Constraints - no implementation code before the plan is written down - test-driven: write the test, watch it fail for the right reason, then implement - systematic debugging — form a hypothesis and test it; never change code hoping it helps - dispatch independently verifiable subtasks to separate agents rather than holding everything in one context - use a worktree for parallel or risky work so the main branch stays clean - verification before completion is mandatory: a task is not done because the code loo