Superpowers

Plugin superpowers from marketplace frad-dotclaude in FradSer/dotclaude. Commands read from the repo's manifest — 6 days ago.

Skills (8)

• behavior-driven-development

  Applies 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.

• brainstorming

  Designs 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). Use when starting a new feature, greenfield design, or multi-comp

• executing-plans

  Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches. Use when a plan exists and the user wants it executed, or invokes /superpowers:executing-plans <plan-path>.

• receiving-code-review

  Use 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.

• retrospective

  Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly. Use after executing-plans completes, or when the user asks to review completed plans and update the checklists via /superpowers:retrospective.

• systematic-debugging

  Diagnoses a reported bug, error, test failure, or unexpected behavior through a 4-phase root-cause analysis before any code changes. Use when the user reports a bug or test failure with an unknown root cause, or invokes /superpowers:systematic-debugging "<symptom>". Not for bugs with a named root ca

• verification-before-completion

  Use 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.

• writing-plans

  Creates executable implementation plans that break down a brainstorming design into detailed, unambiguous per-batch tasks for execution. Use when a design exists and the user wants an implementation plan, or invokes /superpowers:writing-plans <design-path>.

Subagents (1)

• superpowers-evaluator

  Use this agent when the superpowers workflow needs an independent read-only verdict on a design folder or a sprint batch. Spawn with `design` mode against design folders (`_index.md`, `bdd-specs.md`, `architecture.md`, `best-practices.md`) or `code` mode against sprint contracts (`sprint-contract-ba

Hooks (1)

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/stop-state-sync.sh

Similar plugins