Skip to content

What Is Superpowers? The Skills Pack That Teaches Claude Code to Plan, Test First and Review

You install Superpowers in your coding agent (Claude Code, Codex, Cursor and others); before starting work, the agent asks what you want, gets the design approved, writes a plan, implements it test-first and has the work reviewed. It contains 15 skills; they kick in on their own, so you don't need to call them one by one. It is MIT licensed and free; Claude Code's official marketplace is pinned to an older version (6.4.1), and the author's marketplace is used for the latest version (7.0.0).

What it does
Teaches your coding agent a way of working
Type
Skills pack (15 skills, 1 hook)
Where
Claude Code, Codex, Cursor, Gemini CLI and 12 more environments
In the official marketplace
Pinned to version 6.4.1 (current: 7.0.0)
Windows
The hook needs Git for Windows (bash)
Turkish
Not stated in official sources
Cost
The pack is free, MIT licensed

What does Superpowers do?

Coding agents often start writing code before fully understanding what to do. Superpowers is a methodology pack that tells the agent to stop first and ask what you want, get the design approved, write a plan, implement test-first and review the work. A skill is a ready-made instruction set that tells the assistant how to do a task; Superpowers' skills kick in on their own for the right kind of work. The README describes them as "mandatory workflows, not suggestions".

Asks what you wantClarifies the task through conversation and gets the design approved before writing code.
Writes a planA detailed plan, split into tasks, on a separate git branch.
Test first, then codeImplements with subagents or in a single session.
Reviews and wraps upIndependent review, then merge, open a PR or leave it.
Your instructions take precedence over the skills: you can say "don't use this workflow for this task".

Who it's for: developers who work regularly with Claude Code or a similar agent on code projects and are tired of the agent working without a plan or tests. If you don't write code, it won't help you.

What's inside Superpowers?

The pack carries 15 skills, a SessionStart hook and some helper scripts. There's no separate agent, slash command or MCP server (the old commands were removed in 5.1.0).

SkillWhen it kicks in
using-superpowersAt the start of every conversation: requires checking whether a skill applies and, if so, invoking it before answering
brainstormingBefore creative or building work: asks what you want, writes up the design and gets it approved
using-git-worktreesWhen the work needs isolation: sets up a separate git worktree
writing-plansFor multi-step work: writes a plan split into tasks before touching code
subagent-driven-developmentWhen executing the plan in this session: a fresh subagent and a review per task
executing-plansWhen you say to execute the plan yourself in one session: the agent does the tasks itself, with a single review at the end
test-driven-developmentFor every feature and bug fix: a failing test first, then code
requesting-code-reviewWhen a task is done or before merging: an independent review subagent
receiving-code-reviewWhen review feedback arrives: verifies it before applying it blindly
finishing-a-development-branchWhen the work is done and tests pass: offers merge, open a PR or leave it
systematic-debuggingOn a bug or failing test: a root-cause process before proposing a fix
verification-before-completionBefore saying "done": runs the relevant command and shows the output
dispatching-parallel-agentsWith 2 or more independent tasks: one subagent per task
diagnosing-superpowersWhen a Superpowers session goes badly: produces an evidence-based report from the transcript
writing-skillsWhen writing a new skill: a test-first method adapted to skill writing
  • All at once or one by one: the pack is installed in one go, not picked individually; the skills kick in on their own depending on the type of work.
  • Conflicts: don't install the same pack from two marketplaces at once.

How do you install Superpowers?

Each environment has its own install command and is installed separately. The commands are taken verbatim from the official README and marketplace entries.

Official marketplace (pinned to version 6.4.1)› /plugin install superpowers@claude-plugins-official
Author's marketplace (gets the newer version from the README)› /plugin marketplace add obra/superpowers-marketplace
Then› /plugin install superpowers@superpowers-marketplace
  1. Inside a session, /plugin install doesn't install right away; it opens the plugin's details panel. Choose the scope there: just you, everyone on this project, or just you and only this project.
  2. To activate it right away in the open session, type /reload-plugins or restart Claude Code.
  3. To install from the shell without opening a session: claude plugin install superpowers@claude-plugins-official.

Anthropic's official marketplace entry pins Superpowers to a specific commit (5bf4e78, version 6.4.1); the latest release on GitHub is 7.0.0. If you install from the official marketplace, you won't see the new features in the README. Don't install both.

How to tell it's installed: in Claude Code, check /plugin › Installed, or run claude plugin list in the shell. The README's test: in a new session, type "Let's make a react todo list"; if it works, brainstorming kicks in on its own before any code is written.

How do you use Superpowers?

After installing, you don't need to type any special command: when you ask for a task, the relevant skill kicks in on its own. If you want to call one manually, according to the Claude Code docs plugin skills are invoked as /plugin-name:skill-name (for example /superpowers:brainstorming).

The README's test prompt"Let's make a react todo list"With a working install, the agent asks what you want before writing code.
With your own task"I want to add a CSV export feature to our customer table. First ask what I want, get the design approved, then plan."

If the many steps create friction, say "don't use the Superpowers workflow for this task": according to the skill's own text, your instructions (CLAUDE.md and your direct request) take precedence over the skills.

While working, the skill files create the docs/superpowers/ (design and plan documents), .superpowers/ and .worktrees/ folders in the project; details in the "What does it access?" section.

Which tools does Superpowers work in?

Claude CodeYesVia the official marketplace and the author's marketplace; claude.ai/code cloud sessions don't load a plugin installed on your machine.
Codex (app and CLI)YesThe README lists the install steps.
Cursor, Gemini CLI, GitHub Copilot CLIYesThe README gives an install command for each.
Antigravity, Devin CLI, Factory Droid, Grok Build CLI, Kimi Code, OpenCode, Pi, Qwen Code, Hermes Agent, MuseYesThe README describes the install route; see each environment's own docs for details.
claude.ai chat and CoworkUnclearThe Claude listing page only shows "Install in Claude Code"; whether it can be used in chat is not stated in the official documentation.

"Not in the docs" doesn't mean it doesn't work. The list is compiled from the README and the Claude Code documentation.

What does Superpowers write to my files, and what does it run?

What it writes to your project
  • docs/superpowers/specs and plans: design and plan documents (the design document is committed)
  • .worktrees/: separate worktrees; .superpowers/: subagent working files (kept out of git)
  • Project setup in a new worktree: npm install if there's a package.json, cargo build if there's a Cargo.toml, and so on; then it runs the tests
Hook

In Claude Code, a SessionStart hook runs a local bash script at the start of every session (on startup, clear and after compaction) that adds the text of the using-superpowers skill to the agent's context. According to the Claude Code docs, command hooks run with your full permissions, without isolation; reading the hooks folder before installing is the approach the docs recommend.

Internet and data

The skills and the hook run locally. The only part that sends data is brainstorming's optional visual companion: the logo in its frame is loaded from primeradiant.com with the version number; it can be turned off with three environment variables.

Deletion

It cleans up only the worktrees it created itself; if there are unsaved files it doesn't force-delete, it asks you. It deletes a branch only if you explicitly ask.

Published security advisories

GitHub's repository and global advisory lists and the OSV database list no entries; the repository has no SECURITY.md. No published advisory is listed; this doesn't mean it is safe.

This information is compiled from the official repository; it is not a security audit. The Claude Code docs state that Anthropic doesn't audit the contents of plugins in the official marketplace.

Is Superpowers free?

The pack itself is free and MIT licensed: no account, API key or MCP server needed. The real cost comes from the agent it runs in: Claude Code requires a paid Claude plan or an API account on most surfaces (the desktop app's Code tab requires a paid subscription), and other agents' own plans apply.

Working with subagents can use more tokens because it opens a new implementer and review session for each task. The README gives no cost figure; after installing, the "Always-on" line in the claude plugin details superpowers command shows how many tokens the plugin adds to every session.

Allowed
  • Using, copying, modifying and distributing it, including commercially (MIT)
Not allowed
  • Removing the copyright and license notice from copies

Source: LICENSE (MIT, copyright holder Jesse Vincent) and README. The README also says Prime Radiant can be contacted for enterprise use. This is not legal advice.

Common problems and fixes

What happensWhat to do
On Windows, "SessionStart hook error" appears at session start, or the agent doesn't remember Superpowers at allThe hook runs with bash: Git for Windows must be installed. In version 6.4.1 from the official marketplace, if bash isn't found the hook exits silently and no session-start context is added. The 7.0.0 release notes list fixes for this.
Skills don't trigger after installation, or the plugin doesn't appearCheck whether it's listed under /plugin › Installed and in claude plugin list. If you installed it inside a session, run /reload-plugins or open a new session. Don't install the plugin from two marketplaces at once.
Reported by users Slowness, tokens or session limits running out quickly, many steps even for small tasksA common report in GitHub, Hacker News and YouTube comments. On the official side: the README describes executing-plans as the cheapest route; you can also say "don't use the Superpowers workflow for this task".
The /brainstorm, /write-plan, /execute-plan commands from older tutorials don't existRemoved in 5.1.0. Skills kick in on their own or are called like /superpowers:brainstorming. The Claude listing page still describes the old commands.
After installing from the official marketplace, I don't see the new features from the READMEThe official marketplace entry is pinned to 6.4.1. For 7.0.0, use the author's marketplace (superpowers-marketplace); don't install both.
A docs/superpowers/ or .worktrees/ folder appeared where I didn't expect itThe write locations are fixed in the skills: docs/superpowers/specs and plans, .superpowers/, .worktrees/. No configurable environment variable is documented; Reported by users there are requests on GitHub to make this configurable.

How do you disable or uninstall Superpowers?

  1. In Claude Code: Select Superpowers under /plugin › Installed; choose Disable or Uninstall. In the shell: claude plugin disable superpowers@<marketplace> or claude plugin uninstall superpowers@<marketplace>; the marketplace name is claude-plugins-official or superpowers-marketplace.
  2. If you installed it at project scope Claude Code asks whether to disable it just for you or remove it for everyone.
  3. Folders created: docs/superpowers/, .superpowers/ and .worktrees/ are the project's own files; the official docs say they aren't deleted on uninstall. You can list worktrees with git worktree list and remove them yourself.
  4. Other environments: The README only gives install and update commands; to uninstall, use the environment's own plugin management.

To opt out without disabling it completely, it's enough to say "don't use the Superpowers workflow for this task" or pick the "skip questions" option in brainstorming's first message.

Frequently asked questions

What is Superpowers?

A free, MIT-licensed skills pack that teaches your coding agent a software development methodology. With 15 skills, the agent asks what you want before starting, gets the design approved, writes a plan, implements test-first and has the work reviewed.

How do I install Superpowers in Claude Code?

In Claude Code, type /plugin install superpowers@claude-plugins-official and choose the scope in the panel that opens. This official marketplace entry is pinned to version 6.4.1; for the latest version (7.0.0), first type /plugin marketplace add obra/superpowers-marketplace, then /plugin install superpowers@superpowers-marketplace.

Is Superpowers free?

The pack is free and MIT licensed. Costs come from the plan of the agent it runs in and the tokens used; Claude Code requires a paid Claude plan or an API account on most surfaces. Working with subagents can use more tokens.

Which tools does Superpowers work in?

The README describes installation for Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI and Antigravity, Devin CLI, Factory Droid, Grok Build CLI, Kimi Code, OpenCode, Pi, Qwen Code, Hermes Agent, Muse. It is installed separately in each environment.

Do I need to call the skills one by one?

No, the skills kick in on their own depending on the type of work. If you want to call one manually, type something like /superpowers:brainstorming. Your instructions take precedence over the skills: you can say not to use it for a task.

What does Superpowers write to my files?

It creates the docs/superpowers/ (design and plan documents), .superpowers/ and .worktrees/ folders in the project and opens a separate git branch and worktree. In the worktree it can run project setup (such as npm install) and the tests. It asks you before deleting anything.

Does Superpowers collect data?

The skills and the hook run locally. The only part that sends data is brainstorming's optional visual companion: the logo in the frame is loaded from primeradiant.com with the version number, and it can be turned off with three environment variables.

Does Superpowers work on Windows?

The hook requires bash: on Windows, Git for Windows must be installed. In version 6.4.1 from the official marketplace, if bash isn't found the hook exits silently and no session-start context is added; the 7.0.0 notes list fixes for this.

How do I disable or uninstall Superpowers?

In Claude Code, choose Disable or Uninstall under /plugin > Installed; in the shell, claude plugin uninstall superpowers@<marketplace>. To opt out without disabling it completely, just tell it not to use it for a task.

Tasks and setup kits that use Superpowers

Related guides

Sources

Not clear in the official sources: Whether Codex, Cursor and other marketplaces actually list Superpowers (only the README says so) · whether it can be used in claude.ai chat · real token and cost figures (the README gives none) · reply quality in Turkish · when the official marketplace pin will be updated. Each is covered in the relevant section, along with what you can do.