superpowerslisted

# Superpowers — Skill Forge > "14-skill power pack" ## When to use - End-to-end feature work that deserves discipline — "let's build this properly, not vibe-code it" - A bug that resists poking — "debug this systematically", "it fails randomly and I'm lost" - Pre-merge and pre-ship gates — "review my diff", "run a security pass", "are we ready to release?" - After an incident — "write the postmortem" - Any single phase named outright — spec it, plan it, refactor it, profile it, document it ## The 14 protocols | # | Protocol | Core move | |---|---|---| | P1 | Brainstorm | Generate 3+ approaches, score against constraints, pick one on the record. | | P2 | Spec | Acceptance criteria and non-goals written before any code. | | P3 | Plan | Ordered steps, each independently verifiable. | | P4 | Scaffold | Skeleton with tooling wired — lint, test runner, entry point, CI hook. | | P5 | TDD | Red-green-refactor: failing test first, minimal pass, then clean. | | P6 | Systematic debugging | Reproduce → isolate → hypothesize → fix → regress. | | P7 | Refactoring | Behavior-preserving change under green tests, one move at a time. | | P8 | Code review | Line-level and design-level pass — correctness, security, perf, readability. | | P9 | Performance pass | Measure first, profile the hot path, fix, re-measure. | | P10 | Security pass | Inputs, authn/z, secrets, dependencies, injection surfaces. | | P11 | Docs | README, API reference, runbook — written from the reader's seat. | | P12 | G