ClaudeSuperPower

superpowers

Plugin

Superpowers teaches Claude brainstorming, subagent driven development with built in code review, systematic debugging, and red/green TDD. Additionally, it teaches Claude how to author and test new skills.

Install

claude plugin install superpowers@claude-plugins-official

What is superpowers?

Superpowers teaches Claude brainstorming, subagent driven development with built in code review, systematic debugging, and red/green TDD. Additionally, it teaches Claude how to author and test new skills.

What's inside

15 bundled components — installing the plugin installs all of them.

Skills (14)

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Name also used by claude-skills-journalism, open-design

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Name also used by claude-skills-journalism

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Name also used by claude-skills-journalism

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Name also used by claude-skills-journalism

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

Name also used by claude-skills-journalism

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Name also used by claude-skills-journalism

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

Name also used by claude-skills-journalism

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Name also used by claude-skills-journalism

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

Name also used by claude-skills-journalism

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

Name also used by claude-skills-journalism

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

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

Name also used by claude-skills-journalism

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

Name also used by claude-skills-journalism

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Name also used by claude-skills-journalism

What this can do

Capabilities declared by the plugin's own components — read straight from their frontmatter, not inferred.

Inherit all session tools

14 components declare no tool restrictions

~465 tokens of context used while enabled, before you invoke anything

Trust

94/100 · Excellent

1 factor scored below maximum

Unscoped tools

Documentation

README · ~6 min read

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, Antigravity, Codex App, Codex CLI, Cursor, Factory Droid, Gemini CLI, GitHub Copilot CLI, Kimi Code, OpenCode, Pi.

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.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just plugins.