explaingit

obra/superpowers

★ 180,523ShellAudience · developerComplexity · 2/5Setup · easy

TLDR

Superpowers is a plugin for AI coding agents like Claude Code, Cursor, and Codex that enforces a disciplined workflow, brainstorm a spec first, break it into tasks, implement with test-driven development, then run a two-stage code review.

Mindmap

mindmap
  root((superpowers))
    What it does
      Spec before code
      Task breakdown
      Two-stage review
    Workflow
      Brainstorm phase
      Implementation plan
      Test-driven dev
    Skills
      Git worktrees
      Code review
      Debugging
    Audience
      AI tool power users
      Disciplined developers
    Setup
      Plugin marketplace
      Codex CLI plugins
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Add structured spec-writing and planning to your Claude Code or Cursor agent before it writes any code.

USE CASE 2

Enforce test-driven development on an AI coding assistant using a built-in RED-GREEN-REFACTOR workflow.

USE CASE 3

Use the code review skill to have a fresh AI subagent check spec compliance and code quality after each task.

USE CASE 4

Set up git worktrees with Superpowers to run multiple AI coding tasks in parallel without conflicts.

Tech stack

Shell

Getting it running

Difficulty · easy Time to first run · 5min

Installation varies per coding harness, Claude Code uses the plugin marketplace, Codex CLI uses /plugins, separate flows exist for Cursor and Copilot CLI.

License not stated in the explanation.

In plain English

Superpowers is, in the README's own words, "a complete software development methodology for your coding agents, built on top of a set of composable skills and some initial instructions that make sure your agent uses them." A coding agent here is an AI assistant that writes code on your behalf inside a tool like Claude Code, Codex CLI, Cursor, Gemini CLI, or GitHub Copilot CLI. Superpowers is a plugin that ships into that agent and changes how it behaves on a coding task. The way it works, per the README, is that when you fire up your agent on a build task it does not jump straight into writing code. Instead it starts a brainstorming phase, asks what you are really trying to do, and teases a spec out of the conversation. After you sign off, the agent produces an implementation plan broken into small tasks (each with file paths, code, and verification steps), then launches a "subagent-driven-development" process where fresh subagents work through each task and a two-stage review checks spec compliance and code quality. The methodology emphasizes test-driven development (RED-GREEN-REFACTOR), YAGNI, and DRY, with companion skills for git worktrees, code review, finishing a branch, systematic debugging, and writing new skills. Someone would use Superpowers when they want their coding agent to follow a disciplined workflow, design first, plan, test-first implementation, review, instead of cowboy-coding. Installation differs per harness: Claude Code via the plugin marketplace, Codex CLI and App via /plugins, plus separate flows for Factory Droid, Gemini CLI, OpenCode, Cursor, and Copilot CLI.

Copy-paste prompts

Prompt 1
I just installed Superpowers in Claude Code. Walk me through the brainstorming phase, what questions will the agent ask before it starts writing code?
Prompt 2
Using the Superpowers methodology, help me write a spec for adding user authentication to my Node.js app before any code is written.
Prompt 3
Show me how to create a new custom Superpowers skill for systematically debugging Python async code.
Prompt 4
I want to use Superpowers' subagent-driven-development flow to implement a REST API in Go. Explain how the planning and task breakdown work.
Prompt 5
How do I use the Superpowers git worktree skill to run two coding tasks in parallel without them interfering with each other?
Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub obra on gitmyhub

Verify against the repo before relying on details.

Related repos