obra-superpowers

Convert engineering requests into specs, TDD-oriented plans, and verified execution steps.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill obra-superpowers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obra-superpowers
Source: https://github.com/droxey/skills/tree/main/obra-superpowers
Command: npx skills add https://github.com/droxey/skills --skill obra-superpowers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents fragile, regression-prone engineering work by enforcing a disciplined process that clarifies goals, plans small, executes deliberately, and validates changes with evidence.

Core Features & Use Cases

  • Spec-first execution: Converts an engineering request into a short, reviewable spec with clear scope, non-goals, and acceptance criteria.
  • Small TDD-oriented tasks: Breaks implementation into independently verifiable steps, prioritizing true red-green-refactor when tests are practical.
  • Risk review and verification: Performs a pre-flight risk check and requires concrete verification (tests, linters, builds, smoke checks) before claiming completion.

Quick Start

Use the obra-superpowers skill to turn your engineering request into a spec, a small TDD-oriented plan, step-by-step execution guidance, and evidence-based verification.

Frequently Asked Questions about obra-superpowers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce regressions during software engineering refactors and debugging?▼

To reduce regressions during refactors and debugging, enforce a disciplined clarify-spec-plan-execute-verify workflow that captures acceptance criteria, plans small reviewable tasks, and validates changes with concrete evidence.

What is spec-first execution for engineering workflows?▼

Spec-first execution is a process that converts an engineering request into a short, reviewable specification with clear scope, non-goals, and acceptance criteria before any code is written or modified.

How do I implement TDD-oriented tasks for multi-file feature work?▼

Implement TDD-oriented tasks by breaking multi-file feature work into independently verifiable steps, prioritizing true red-green-refactor cycles when practical, and running targeted verification outputs before completion.

Can I use this disciplined engineering workflow for code review and multi-agent coordination?▼

Yes, this engineering workflow applies directly to code review and multi-agent implementation coordination, ensuring careful change management by requiring pre-flight risk checks and avoiding unverifiable claims of completion.

What's the best way to verify code changes and avoid false claims of completion?▼

The best way to verify code changes is to perform a pre-flight risk review and require concrete verification outputs, such as tests, linters, builds, and smoke checks, before claiming any task is complete.