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
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
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
- Version
- 7.0.1, released 2026-10-21
- Last commit
- 2026-10-21 on main
- Created
- 2025-10-09
- Official listing
- Anthropic official marketplace, marked Anthropic verified
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 ·
brainstormingTurns 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-plansCreates 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-worktreesBuilds 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-developmentBuilds 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-plansWrites 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-developmentFinds 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-debuggingMakes 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-completionReviews finished work against the requirements
Checks a finished task or feature against the plan and requirements before merging.
Read ·
requesting-code-reviewChecks review feedback instead of agreeing blindly
When review comments arrive, Claude tests whether they are technically right before changing code.
Read ·
receiving-code-reviewSplits 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-agentsOffers 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-branchGuide for creating and testing your own skills
Helps you write, edit and test new skills of your own.
Try: “Help me write a new skill”
Write ·
writing-skillsExplains from a transcript why Superpowers misbehaved
Reads past session transcripts, reports what went wrong with evidence and can build a scrubbed bug report. It files a GitHub issue only after you approve the text.
Try: “figure out what went wrong with superpowers in this session”
Network ·
diagnosing-superpowersUsed by the assistant behind the scenes
Tells Claude to check for a relevant skill before replying
Loaded at the start of every session. It makes Claude look for a matching skill before it answers.
Read ·
using-superpowersLoads the using-superpowers skill into each new session
Runs a bash script on startup, /clear and compaction. It reads the using-superpowers skill from disk and adds it to Claude's context. No network calls.
Runs code ·
SessionStart hookOptional local web page for visual brainstorming
A Node server on 127.0.0.1 at a random port that shows mockups while you brainstorm. It stops after 4 hours idle and loads its logo from primeradiant.com.
Runs code ·
Visual companion server
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-only | No 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 to | primeradiant.com (optional visual brainstorming page loads its logo with the Superpowers version) |
| Data retention | No 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
“For what it's worth, I really enjoy superpowers. In particular, it does a great job with TDD that stops the model from jumping to conclusions, and I've been able to get it, even with Opus, to execute on much longer specs quite well.”prplfshHacker NewsJul 2026
“I gave Superpowers 5.x a whirl for a week, and aside from consuming a stupid amount of tokens, it did materially worse across all my personal benchmarks and general day-to-day development compared to plain Codex/Claude.”artisinHacker NewsJul 2026
“Yes, it's SUPER slow. For a laugh, you can ask it to make a change you know can be done in one line. It'll do it in one line, but it take literally an hour with all the verification. But that's sort of the point.”tmach32GitHub issueMar 2026
“Many of my requests normally complete in under 10 minutes, but now some are taking 30 to 45 minutes for the same size, complexity, and code. :(”OZRay888
1 more quoteFewer quotes
Included in this plugin
15
- brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
414K installs - diagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for
25K installs - dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
225K installs - executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
250K installs - finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
221K installs - receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
228K installs - requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
269K installs - subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
245K installs - systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
316K installs - test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
267K installs - using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
223K installs - using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
277K installs - verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
261K installs - writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
291K installs - writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
225K installs
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
- Repository
- obra/superpowers
Sources
Docs, issue trackers and discussions this page is built from.
Show all 33Hide
- Anthropic official marketplace · github.com
- Superpowers marketplace · github.com
- Codex app · github.com
- Codex CLI · github.com
- Superpowers marketplace · github.com
- Agent chat · github.com
- Gemini CLI extension · github.com
- Ask OpenCode · github.com
- The basic workflow · github.com
- Superpowers discussion · blog.fsck.com
- obra/superpowers README · github.com
- Created · blog.fsck.com
- License · github.com
- Version · github.com
- Last commit · github.com
- skills folder · github.com
- Works in · github.com
- Superpowers on claude.com · claude.com
- hooks.json · github.com
- claude-plugins-official marketplace.json · github.com
- Skills in obra/superpowers · github.com
- Visual companion · github.com
- session-start script · github.com
- Visual companion telemetry · github.com
- diagnosing-superpowers: GitHub issues · github.com
- Release notes · github.com
- When something goes wrong · github.com
- Superpowers 6 (HN comment) · news.ycombinator.com
- Superpowers 6 (HN comment) · news.ycombinator.com
- Superpowers discussion · news.ycombinator.com
- Superpowers discussion · news.ycombinator.com
- Superpowers discussion · news.ycombinator.com
- Superpowers discussion · github.com