Superpowers
by @fradser · plugin · 8 skills
Advanced development workflow orchestration with BDD support and self-improving skills
Install the whole plugin (CLI)
npx skillmds add fradser/brainstorming
npx skillmds add fradser/retrospective
npx skillmds add fradser/writing-plans
npx skillmds add fradser/executing-plans
npx skillmds add fradser/systematic-debugging
npx skillmds add fradser/receiving-code-review
npx skillmds add fradser/behavior-driven-development
npx skillmds add fradser/verification-before-completionSkills in this plugin
- ▌ brainstorming · fradser bundleDesigns new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).
- ▌ retrospective · fradser bundleAnalyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.
- ▌ writing-plans · fradser bundleCreates executable implementation plans that break down a brainstorming design into detailed, unambiguous per-batch tasks for execution.
- ▌ executing-plans · fradser bundleExecutes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.
- ▌ systematic-debugging · fradser bundleDiagnoses a reported bug, error, test failure, or unexpected behavior through a 4-phase root-cause analysis before any code changes.
- ▌ receiving-code-review · fradserUse when the superpowers-evaluator returned REWORK on a batch, when fixing rework items from an evaluation report, or when receiving any code review feedback on superpowers output. Requires technical rigor and verification instead of performative agreement or blind implementation.
- ▌ behavior-driven-development · fradser bundleApplies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
- ▌ verification-before-completion · fradserUse when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.