PlugWiki

Superpowers plugin for Claude Code

Jesse Vincent's free plugin that makes Claude Code brainstorm, plan, write tests first and review its own work.

Skills
15
included
Hooks
1
included
Stars
310.6K
on GitHub
Included
15
listed

Superpowers makes Claude Code follow a fixed build routine. It asks what you want, writes a plan, builds with tests first and reviews the result before it calls the job done. The skills start on their own, so you do not call them one by one. Know before you install: it is thorough and slow, and the author says it uses a lot of tokens.

Good for

  • Developers who want Claude to write tests before code
  • Teams handing Claude multi-hour feature work
  • Anyone debugging with Claude who wants root causes, not guesses
  • People who write their own skills

Install superpowers

Claude Code

  1. 1

    Copy this prompt.

    Install the superpowers plugin in Claude Code. Run this command:
    
    /plugin install superpowers@claude-plugins-official
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Install from one of these two marketplaces only. Repos with the same name under other owners are not Jesse Vincent's plugin.

From the project README. Source.

Key facts

License
MIT, free
Created
2025-10-09

What it includes

  • Asks what you want, then writes a design for you to approve

    Before any creative work, Claude asks questions about what you want and writes a design doc. You approve it before any code is written.

    Try: “Let's make a react todo list”

    Write · brainstorming

  • Turns the approved design into small step-by-step tasks

    Breaks the design into short tasks with exact file paths, complete code and checks, so work can start without guessing.

    Try: “Write the implementation plan for this design”

    Write · writing-plans

  • Creates a separate branch and workspace before feature work

    Gives the work its own git worktree so your main checkout stays untouched while Claude builds.

    Runs code · using-git-worktrees

  • Builds the plan with a fresh subagent and review per task

    Hands each task to a new subagent and reviews it before the next. The most thorough option, and the slowest and most token-hungry.

    Try: “Execute this plan with subagent-driven-development”

    Runs code · subagent-driven-development

  • Builds the plan in this session with one review at the end

    The cheaper way to run a plan: every task runs in the current session and you get one final review.

    Try: “Execute this plan with executing-plans”

    Runs code · executing-plans

  • Writes a failing test first, then the code

    Enforces red, green, refactor. Claude must see a test fail before it writes the code, and code written before tests is deleted.

    Runs code · test-driven-development

  • Finds the root cause before proposing any fix

    Runs a four-phase investigation of a bug or failing test before Claude suggests a change.

    Try: “Use systematic-debugging on this failing test”

    Runs code · systematic-debugging

  • Makes Claude run checks before saying it is done

    Claude must run the verification commands and read their output before it claims work is finished.

    Runs code · verification-before-completion

  • Reviews finished work against the requirements

    Checks a finished task or feature against the plan and requirements before merging.

    Read · requesting-code-review

  • Checks review feedback instead of agreeing blindly

    When review comments arrive, Claude tests whether they are technically right before changing code.

    Read · receiving-code-review

  • Splits independent tasks across parallel subagents

    When two or more tasks do not depend on each other, runs them side by side.

    Runs code · dispatching-parallel-agents

  • Offers merge, PR, keep or discard when tests pass

    Once tests pass, gives you the choice to merge, open a pull request, keep or discard the branch, then cleans up the worktree.

    Runs code · finishing-a-development-branch

From the official docs

Permissions

Low risk

The main risk is installing a copy that only shares the name, since Claude then follows instructions from a stranger. Install from the official Anthropic marketplace and keep Claude Code's permission prompts on.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Copies named superpowers are not this plugin

    Many unrelated repos copy the name. The real one is obra/superpowers by Jesse Vincent, the source Anthropic's official marketplace points to. Install from the official marketplace and check the owner is obra. github.com

  • That page sends the Superpowers version to primeradiant.com

    Its logo loads from primeradiant.com with the version number. The README says no project or prompt data is sent. Turn it off with SUPERPOWERS_DISABLE_TELEMETRY. github.com

  • A startup hook runs a script in every new session

    One SessionStart hook (on startup, /clear and compaction) runs the plugin's session-start bash script. It reads the using-superpowers skill from disk and adds it to Claude's context. It makes no network calls. github.com

  • Claude is told to write files, commit and merge

    The skills ask Claude to create worktrees and branches, edit code and commit. Keep Claude Code's permission prompts on and read what it proposes before merges. github.com

  • Optional local web page for visual brainstorming

    If you accept it, a Node server starts on 127.0.0.1 at a random port with a key in the URL and stops after 4 hours idle. Do not bind it to a non-local address unless you need a remote setup. github.com

  • The diagnosing skill reads your past sessions

    diagnosing-superpowers reads session transcripts to explain a misfire. It files a GitHub issue only after you approve the exact text, and bug bundles are scrubbed first. github.com

  • Helper scripts run on your machine

    Some skills ship shell and Node scripts (for example find-polluter.sh) that Claude runs locally. They are plain files in the plugin folder you can read first. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only mode. The skills tell Claude to create git worktrees, write design docs, plans, tests and code, commit, and merge or open pull requests with options offered to you. Claude Code's own permission prompts still apply.
Talks toprimeradiant.com (optional visual brainstorming page loads its logo with the Superpowers version)
Data retentionNo Superpowers servers store your prompts or code. The only outbound request is the optional visual companion logo.

What people say

People credit it with more disciplined, spec-faithful code and complain about the time and tokens it costs.

What people like

  • Test-first rule stops Claude jumping to conclusions and helps it carry out longer specs.
  • Per-task review of spec and code quality gives code that follows the spec more closely.
  • Users say version 6 uses noticeably fewer tokens, as the author claimed.

Common complaints

  • Uses many tokens and is slow, even for small changes.
  • You cannot switch it on only for big jobs; the test and verification steps run on trivial edits too.
  • Version 7 brainstorming opens with generic questions; some long-time users want the old behavior back.

In their words

1 more quote

Included in this plugin

15

Questions

Which superpowers repo is the real one?

The real one is obra/superpowers by Jesse Vincent (Prime Radiant). Anthropic's official marketplace lists superpowers with that repo as its source, and the claude.com listing links to it. Other repos named superpowers are not this project, so install from the official marketplace.

How do I install the Superpowers plugin in Claude Code?

Use the install box at the top of this page. The official Anthropic marketplace option is the safest default. The author's own marketplace works too.

Is Superpowers safe?

Mostly yes. It is MIT licensed, has no published security advisories and its one hook only reads a file on your machine. The real risks are installing a lookalike repo and letting Claude commit and merge without checking.

Does Superpowers still have /brainstorm, /write-plan and /execute-plan?

No. They were removed in version 5.1.0. The skills start on their own, or you can name them directly, for example superpowers:brainstorming.

Does Superpowers use a lot of tokens?

Yes. The author says Superpowers uses a ton of tokens, and wrote that version 6 made builds up to 50% faster and up to 60% cheaper. The executing-plans skill is cheaper than subagent-driven-development, which reviews after every task.

Does Superpowers send any data out?

Only the optional visual brainstorming page does. It loads a logo from primeradiant.com with the Superpowers version number. You can turn that off with SUPERPOWERS_DISABLE_TELEMETRY, DISABLE_TELEMETRY or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC.

Does Superpowers work in Codex, Cursor or the Claude app?

Codex and Cursor, yes: the README documents install for both, plus Gemini CLI, Copilot CLI, OpenCode and others. Install it separately in each tool. The README has no setup for the Claude desktop app or VS Code Copilot.

Is Superpowers free?

Yes. It is free and MIT licensed. Prime Radiant sells commercial support to enterprise users.

Superpowers vs GSD or Matt Pocock's skills?

Superpowers imposes a full routine: brainstorm, worktree, plan, build with tests and review. On Hacker News one user said Matt Pocock's skills gave good results without burning as many tokens, and another asked how it compares with GSD. No shared benchmark compares them.

What do I do when Superpowers misbehaves?

Ask Claude to figure out what went wrong with superpowers in this session. The diagnosing-superpowers skill reads the transcript and can prepare a scrubbed bug report.

Information

updated Nov 2, 2026

Runs in
Claude Code

obra/superpowers

Sources

Docs, issue trackers and discussions this page is built from.

Show all 33
  1. Anthropic official marketplace · github.com
  2. Superpowers marketplace · github.com
  3. Codex app · github.com
  4. Codex CLI · github.com
  5. Superpowers marketplace · github.com
  6. Agent chat · github.com
  7. Gemini CLI extension · github.com
  8. Ask OpenCode · github.com
  9. The basic workflow · github.com
  10. Superpowers discussion · blog.fsck.com
  11. obra/superpowers README · github.com
  12. Created · blog.fsck.com
  13. License · github.com
  14. Version · github.com
  15. Last commit · github.com
  16. skills folder · github.com
  17. Works in · github.com
  18. Superpowers on claude.com · claude.com
  19. hooks.json · github.com
  20. claude-plugins-official marketplace.json · github.com
  21. Skills in obra/superpowers · github.com
  22. Visual companion · github.com
  23. session-start script · github.com
  24. Visual companion telemetry · github.com
  25. diagnosing-superpowers: GitHub issues · github.com
  26. Release notes · github.com
  27. When something goes wrong · github.com
  28. Superpowers 6 (HN comment) · news.ycombinator.com
  29. Superpowers 6 (HN comment) · news.ycombinator.com
  30. Superpowers discussion · news.ycombinator.com
  31. Superpowers discussion · news.ycombinator.com
  32. Superpowers discussion · news.ycombinator.com
  33. Superpowers discussion · github.com

Updated Nov 2, 2026.