Superpowers

Superpowers is 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.

Quickstart

Give your agent Superpowers: Claude Code, Codex CLI, Codex App, Factory Droid, Gemini CLI, OpenCode, Cursor, GitHub Copilot CLI.

How it works

It starts from the moment you fire up your coding agent. As soon as it sees that you're building something, it doesn't just jump into trying to write code. Instead, it steps back and asks you what you're really trying to do.

Once it's teased a spec out of the conversation, it shows it to you in chunks short enough to actually read and digest.

After you've signed off on the design, your agent puts together an implementation plan that's clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing to follow. It emphasizes true red/green TDD, YAGNI (You Aren't Gonna Need It), and DRY.

Next up, once you say "go", it launches a subagent-driven-development process, having agents work through each engineering task, inspecting and reviewing their work, and continuing forward. It's not uncommon for Claude to be able to work autonomously for a couple hours at a time without deviating from the plan you put together.

There's a bunch more to it, but that's the core of the system. And because the skills trigger automatically, you don't need to do anything special. Your coding agent just has Superpowers.

VKirill Fork Notes

This fork keeps the upstream Superpowers workflow intact, but adds a small set of Codex-focused skill updates. The goal is practical: preserve local review and verification improvements so marketplace/plugin updates do not wipe them out.

The changes are intentionally limited to existing skill prompts. No new skills, dependencies, or plugin bootstrap behavior were added.

What Changed

• Code review is stricter and more concrete. requesting-code-review now asks reviewers to check tests first, then review correctness, readability, architecture, security, performance, production readiness, verification evidence, dependency impact, and documentation/ADR needs.
• Reviewers get change-size guidance. The reviewer prompt now treats about 100 changed lines as easy to review, about 300 as acceptable for one logical change, and about 1000 as a signal to split the work. Large deletions and mechanical refactors can still be fine when the intent is easy to verify.
• Tool-assisted review is explicit. Reviewers may use Serena for symbol navigation, GitNexus for blast-radius checks, docs MCP tools for version-sensitive APIs, and browser/runtime tools for UI behavior when those tools are available and relevant.
• Implementation agents have tighter scope discipline. subagent-driven-development now tells implementers to work in the smallest complete slice, avoid unrelated cleanup, avoid formatting churn, and report unrelated issues as "Noticed but not touched" instead of fixing them opportunistically.
• UI completion requires browser evidence. verification-before-completion now calls out browser/runtime verification for UI changes: route loaded, console/network checked, interaction exercised, and layout/text fit inspected where relevant.
• Planning now checks contracts and sources. writing-plans now asks planners to add source-doc checks, public-interface compatibility, external-data validation, dependency justification, and ADR tasks when the change crosses those boundaries.

Files Changed In This Fork

• skills/requesting-code-review/code-reviewer.md
• skills/subagent-driven-development/implementer-prompt.md
• skills/verification-before-completion/SKILL.md
• skills/writing-plans/SKILL.md

Sponsorship

If Superpowers has helped you do stuff that makes money and you are so inclined, I'd greatly appreciate it if you'd consider sponsoring my opensource work.

Thanks!

• Jesse

Installation

Installation differs by harness. If you use more than one, install Superpowers separately for each one.

Claude Code

Superpowers is available via the official Claude plugin marketplace

Official Marketplace

• Install the plugin from Anthropic's official marketplace:

  /plugin install superpowers@claude-plugins-official

Superpowers Marketplace

The Superpowers marketplace provides Superpowers and some other related plugins for Claude Code.

• Register the marketplace:

  /plugin marketplace add obra/superpowers-marketplace

• Install the plugin from this marketplace:

  /plugin install superpowers@superpowers-marketplace

Codex CLI

Superpowers is available via the official Codex plugin marketplace.

• Open the plugin search interface:

  /plugins

• Search for Superpowers:

  superpowers

• Select Install Plugin.

Codex App

Superpowers is available via the official Codex plugin marketplace.

• In the Codex app, click on Plugins in the sidebar.
• You should see Superpowers in the Coding section.
• Click the + next to Superpowers and follow the prompts.

Factory Droid

• Register the marketplace:

  droid plugin marketplace add https://github.com/obra/superpowers

• Install the plugin:

  droid plugin install superpowers@superpowers

Gemini CLI

• Install the extension:

  gemini extensions install https://github.com/obra/superpowers

• Update later:

  gemini extensions update superpowers

OpenCode

OpenCode uses its own plugin install; install Superpowers separately even if you already use it in another harness.

• Tell OpenCode:

  Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.opencode/INSTALL.md
  

• Detailed docs: docs/README.opencode.md

Cursor

• In Cursor Agent chat, install from marketplace:

  /add-plugin superpowers
  

• Or search for "superpowers" in the plugin marketplace.

GitHub Copilot CLI

• Register the marketplace:

  copilot plugin marketplace add obra/superpowers-marketplace

• Install the plugin:

  copilot plugin install superpowers@superpowers-marketplace

The Basic Workflow

1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

3. writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.

4. subagent-driven-development or executing-plans - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.

5. test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.

6. requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

7. finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.

The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.

What's Inside

Skills Library

Testing

• test-driven-development - RED-GREEN-REFACTOR cycle (includes testing anti-patterns reference)

Debugging

• systematic-debugging - 4-phase root cause process (includes root-cause-tracing, defense-in-depth, condition-based-waiting techniques)
• verification-before-completion - Ensure it's actually fixed

Collaboration

• brainstorming - Socratic design refinement
• writing-plans - Detailed implementation plans
• executing-plans - Batch execution with checkpoints
• dispatching-parallel-agents - Concurrent subagent workflows
• requesting-code-review - Pre-review checklist
• receiving-code-review - Responding to feedback
• using-git-worktrees - Parallel development branches
• finishing-a-development-branch - Merge/PR decision workflow
• subagent-driven-development - Fast iteration with two-stage review (spec compliance, then code quality)

Meta

• writing-skills - Create new skills following best practices (includes testing methodology)
• using-superpowers - Introduction to the skills system

Philosophy

• Test-Driven Development - Write tests first, always
• Systematic over ad-hoc - Process over guessing
• Complexity reduction - Simplicity as primary goal
• Evidence over claims - Verify before declaring success

Read the original release announcement.

Contributing

The general contribution process for Superpowers is below. Keep in mind that we don't generally accept contributions of new skills and that any updates to skills must work across all of the coding agents we support.

1. Fork the repository
2. Switch to the 'dev' branch
3. Create a branch for your work
4. Follow the writing-skills skill for creating and testing new and modified skills
5. Submit a PR, being sure to fill in the pull request template.

See skills/writing-skills/SKILL.md for the complete guide.

Updating

Superpowers updates are somewhat coding-agent dependent, but are often automatic.

License

MIT License - see LICENSE file for details

Community

Superpowers is built by Jesse Vincent and the rest of the folks at Prime Radiant.

• Discord: Join us for community support, questions, and sharing what you're building with Superpowers
• Issues: https://github.com/obra/superpowers/issues
• Release announcements: Sign up to get notified about new versions