# Superpowers

By **obra** · Skills

Open-source agentic skills framework that brings spec-first, TDD-enforced, subagent-driven software development to Claude Code, Cursor, Codex, and 8 other AI coding harnesses.

- Source: https://github.com/obra/superpowers
- Repository: https://github.com/obra/superpowers
- Install: `npm i superpowers`
- Tags: open-source, agent, tdd, workflow, multi-harness, subagent, mit
- Pricing: free
- Upvotes: 0

## Features

- Composable SKILL.md library covering TDD, debugging, brainstorming, planning, subagent dispatch, and code review
- Automatic skill activation via YAML frontmatter; 1% relevance threshold triggers mandatory invocation
- Subagent-driven development: fresh subagent per task with two-stage review (spec compliance, then code quality)
- RED-GREEN-REFACTOR TDD enforcement; deletes code written before tests
- Personal skill shadowing to override built-in skills by name
- Supports 11 coding harnesses: Claude Code, Cursor, Codex App, Codex CLI, Gemini CLI, GitHub Copilot CLI, Kimi Code, Anti
- Git worktree integration for isolated parallel development branches
- writing-skills meta-skill to create and test new custom skills following best practices

---

## Why it matters

Superpowers imposes a full software engineering discipline on coding agents before they write a single line of code. Most agents jump straight to implementation; Superpowers forces a Socratic brainstorm, a human-approved spec, a bite-sized implementation plan, strict RED-GREEN-REFACTOR TDD, and two-stage code review, in that order, every time.

## The big picture

Superpowers is a composable skills framework and development methodology, released by Jesse Vincent and Prime Radiant, licensed MIT. It works across 11 coding harnesses (Claude Code, Cursor, Codex App, Codex CLI, Gemini CLI, GitHub Copilot CLI, Kimi Code, Antigravity, Factory Droid, OpenCode, and Pi) by installing harness-specific plugins or extensions from the GitHub repository at github.com/obra/superpowers.

## How it works

Each skill lives in a `SKILL.md` file with YAML frontmatter that tells the agent when to activate it. Per the `using-superpowers` bootstrap skill, the agent must invoke any skill with even a 1% chance of relevance, and skill invocations are mandatory, not optional. The priority chain is clear: user instructions in CLAUDE.md or AGENTS.md override skills, skills override default system prompts, and the agent has no way to rationalize itself out of using an applicable skill.

## Zoom in

The core workflow runs seven stages: brainstorming (spec refinement), git worktree setup, plan writing (tasks sized 2-5 minutes each, with exact file paths and verification steps), subagent-driven execution, test-driven development, code review between tasks, and branch finishing. Each stage activates automatically; the agent checks for relevant skills before any task.

## Yes, but

The multi-harness coverage is a genuine strength, but it is also the main maintenance constraint: the README states that skill updates must work across all supported coding agents, and new skill contributions are generally not accepted. Teams running more than one harness must install Superpowers separately per harness, and any customization through personal skill overrides (shadowing) must stay compatible with all targets. If your team has a custom SDLC that conflicts with TDD or YAGNI, skills can be overridden by user instructions, but the defaults will push back hard.

## The bottom line

Superpowers is the sharpest off-the-shelf way to make a coding agent behave like a disciplined engineer rather than an autocomplete engine. Install it once per harness from github.com/obra/superpowers and the methodology runs automatically from the first prompt.

## FAQ

### What is Superpowers?

Superpowers is a complete software development methodology and composable skills framework for AI coding agents, released as MIT open-source by Jesse Vincent and Prime Radiant. It installs as a plugin or extension into your coding harness and automatically enforces a structured workflow: Socratic brainstorm, human-approved spec, detailed plan, strict TDD, subagent-driven execution, and code review, in that order. The skills trigger automatically based on context, so you do not need to prompt for them manually.

### How do I install Superpowers?

Installation is harness-specific and must be done separately for each agent you use. The README at github.com/obra/superpowers documents every supported harness: Claude Code (official Anthropic plugin marketplace or Superpowers marketplace), Cursor (plugin marketplace via /add-plugin), Codex App/CLI (official Codex plugin marketplace), Gemini CLI (gemini extensions install), GitHub Copilot CLI (Superpowers marketplace), Kimi Code (built-in plugin manager), Antigravity, Factory Droid, OpenCode, and Pi. Follow the harness-specific instructions in the README for the correct command.

### Is Superpowers free or open-source?

Superpowers is MIT licensed and fully open-source, hosted at github.com/obra/superpowers. It is free to install and use across all supported harnesses. Prime Radiant offers commercial support, additional tooling, and managed spending for enterprise users via sales@primeradiant.com, but those services are entirely optional.

### What is Superpowers best for?

Superpowers works best for developers who want a coding agent to behave like a disciplined engineer rather than an autocomplete engine. It is especially valuable when you need hours of autonomous agent work that stays on plan, when your team wants TDD and code review enforced automatically, or when you are building something complex enough to need a spec-first approach. Per the README, it is not uncommon for the agent to work autonomously for a couple of hours at a time without deviating from the approved plan.

### How does Superpowers compare to just writing a custom system prompt or CLAUDE.md?

A custom system prompt gives you one-off instructions; Superpowers gives you a versioned, composable library of mandatory workflow skills that activate automatically based on task context. The key difference is the 1% rule: per the using-superpowers bootstrap, the agent must invoke any skill with even a 1% chance of relevance, making the methodology non-negotiable at runtime rather than advisory. Custom instructions can still override any skill, so Superpowers and your own CLAUDE.md or AGENTS.md coexist, with user instructions always taking highest priority.

### What are the limits or tradeoffs I should know about?

Superpowers requires a separate install per coding harness, so teams using multiple agents face compounding maintenance. Upstream contributions of new skills are generally not accepted, meaning you cannot easily extend the shared library. The framework enforces TDD, YAGNI, and DRY by default; teams with different SDLC conventions will need to override skills via user instruction files. Telemetry is on by default (a version-tagged logo load from Prime Radiant's servers) and must be explicitly disabled with the SUPERPOWERS_DISABLE_TELEMETRY environment variable.

---
[View on Analog](https://analoghq.ai/obra/skills/superpowers)