
superpowers
★ 247,050Claude Code plugin · obra/superpowers · MIT
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
14 skills · hooks — installs as one unit
⌁ skills (14)
brainstorming
🔥🔥🔥🔥✓ VerifiedYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Full instructions & audit →dispatching-parallel-agents
🔥🔥🔥🔥✓ VerifiedUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Full instructions & audit →executing-plans
🔥🔥🔥🔥✓ VerifiedUse when you have a written implementation plan to execute in a separate session with review checkpoints
Full instructions & audit →finishing-a-development-branch
🔥🔥🔥🔥✓ VerifiedUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Full instructions & audit →receiving-code-review
🔥🔥🔥🔥✓ VerifiedUse 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
Full instructions & audit →requesting-code-review
🔥🔥🔥🔥✓ VerifiedUse when completing tasks, implementing major features, or before merging to verify work meets requirements
Full instructions & audit →subagent-driven-development
🔥🔥🔥🔥✓ VerifiedUse when executing implementation plans with independent tasks in the current session
Full instructions & audit →systematic-debugging
🔥🔥🔥🔥🔥✓ VerifiedUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Full instructions & audit →test-driven-development
🔥🔥🔥🔥✓ VerifiedUse when implementing any feature or bugfix, before writing implementation code
Full instructions & audit →using-git-worktrees
🔥🔥🔥🔥✓ VerifiedUse 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
Full instructions & audit →using-superpowers
🔥🔥🔥✓ VerifiedUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Full instructions & audit →verification-before-completion
🔥🔥🔥🔥✓ VerifiedUse 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
Full instructions & audit →writing-plans
🔥🔥🔥🔥✓ VerifiedUse when you have a spec or requirements for a multi-step task, before touching code
Full instructions & audit →writing-skills
🔥🔥🔥🔥✓ VerifiedUse when creating new skills, editing existing skills, or verifying skills work before deployment
Full instructions & audit →⌁ also included
- Hooks — automations that run on events (e.g. before/after every edit or commit)
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.
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 your agent 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.
Commercial Services
If you're using Superpowers in enterprise and could benefit from commercial support, additional tooling, or managed spending, please don't hesitate to drop us a line at sales@primeradiant.com.
The Basic Workflow
-
brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.
-
using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
-
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.
-
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.
-
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.
-
requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.
-
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.
Visual companion telemetry
Because skills and plugins don't provide any feedback to creators, we have no idea how many of you are using Superpowers. By default, the Prime Radiant logo on brainstorming's optional visual companion feature is loaded from our website. It includes the version of Superpowers in use. It does not include any details about your project, prompt, or coding agent. We don't see your clicks or anything about what you're building. This helps us have a rough idea of how many folks are using Superpowers and which version of Superpowers they're using. It's 100% optional. To disable this, set the environment variable SUPERPOWERS_DISABLE_TELEMETRY to any true value. Superpowers also honors Claude Code's DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC opt-outs.
Quickstart
Give your agent Superpowers: Claude Code, Antigravity, Codex App, Codex CLI, Cursor, Factory Droid, GitHub Copilot CLI, Kimi Code, OpenCode, Pi.
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
Antigravity
Install Superpowers as a plugin from this repository:
agy plugin install https://github.com/obra/superpowersAntigravity runs the plugin's session-start hook, so Superpowers is active from the first message. Reinstall with the same command to update.
Codex App
Superpowers is available via the official Codex plugin marketplace.
- In the Codex app, click on Plugins in the sidebar.
- You should see
Superpowersin the Coding section. - Click the
+next to Superpowers and follow the prompts.
Codex CLI
Superpowers is available via the official Codex plugin marketplace.
-
Open the plugin search interface:
/plugins -
Search for Superpowers:
superpowers -
Select
Install Plugin.
Cursor
-
In Cursor Agent chat, install from marketplace:
/add-plugin superpowers -
Or search for "superpowers" in the plugin marketplace.
Factory Droid
-
Register the marketplace:
droid plugin marketplace add https://github.com/obra/superpowers -
Install the plugin:
droid plugin install superpowers@superpowers
GitHub Copilot CLI
-
Register the marketplace:
copilot plugin marketplace add obra/superpowers-marketplace -
Install the plugin:
copilot plugin install superpowers@superpowers-marketplace
Kimi Code
Superpowers is available in Kimi Code's plugin marketplace.
-
Open Kimi Code's plugin manager:
/plugins -
Go to
Marketplace>Superpowersand install it. -
Or install directly from this repository:
/plugins install https://github.com/obra/superpowers -
Detailed docs: docs/README.kimi.md
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
Pi
Install Superpowers as a Pi package from this repository:
pi install git:github.com/obra/superpowersFor local development, run Pi with this checkout loaded as a temporary package:
pi -e /path/to/superpowersThe Pi package loads the Superpowers skills and a small extension that injects the using-superpowers bootstrap at session startup and again after compaction. Pi has native skills, so no compatibility Skill tool is required. Subagent and task-list tools remain optional Pi companion packages.
Updating
Superpowers updates are somewhat coding-agent dependent, but are often automatic.
One install gets you everything — 14 skills, hooks — kept up to date together.
Licensed under MIT— you can use, modify, and redistribute it under that license's terms.
License
MIT License - see LICENSE file for details