Superpowers: The Agentic Skills Framework That Makes Claude Code Actually Think Before Coding

The Problem With Every AI Coding Agent Out of the Box

You open Claude Code. You type "build me a user authentication system." And within seconds it's already writing UserController.cs β€” no questions asked, no design discussion, no test strategy. Five hundred lines later, you have something that compiles but doesn't match what you actually needed.

This is the default behavior of every coding agent. Fast. Confident. Frequently wrong about the important parts.

Superpowers (github.com/obra/superpowers) is a plugin that changes that contract. Instead of jumping straight to code, the agent is forced to think first β€” through a structured sequence of skills that mirror how a disciplined senior engineer actually works.


Is It Like get-shit-done?

Short answer: no. They operate at completely different layers.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚              get-shit-done (GSD)                β”‚
β”‚  β†’ Workflow methodology for humans              β”‚
β”‚  β†’ Checklists, git conventions, task mgmt      β”‚
β”‚  β†’ You follow the process manually             β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚              obra/superpowers                   β”‚
β”‚  β†’ Plugin installed INTO the AI agent           β”‚
β”‚  β†’ Skills auto-trigger based on context         β”‚
β”‚  β†’ The agent follows the process, not you       β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

GSD is a discipline system for humans. Superpowers is a behavior injection layer for AI agents. You could use both β€” they don't conflict.


How Superpowers Works

Once installed, the agent loads a set of skills β€” markdown files that define when and how to invoke a specific workflow. The agent checks for relevant skills before any task. These are mandatory workflows, not suggestions.

You: "Add a payment integration"
     β”‚
     β–Ό
[brainstorming] ──→ Clarify scope, explore alternatives
     β”‚                 Output: design doc
     β–Ό
[using-git-worktrees] ──→ Isolated branch, clean baseline
     β”‚
     β–Ό
[writing-plans] ──→ Tasks broken to 2-5 min chunks
     β”‚               Each: exact file path + code + verify step
     β–Ό
[subagent-driven-development]
     β”‚   β”œβ”€ subagent picks up Task #1
     β”‚   β”œβ”€ Stage 1 review: spec compliance
     β”‚   β”œβ”€ Stage 2 review: code quality
     β”‚   └─ repeat per task
     β–Ό
[test-driven-development] ──→ RED β†’ GREEN β†’ REFACTOR
     β”‚                         enforced at every task
     β–Ό
[requesting-code-review] ──→ Critical issues block progress
     β”‚
     β–Ό
[finishing-a-development-branch]
     └─ merge / open PR / discard

The key insight: the agent cannot skip steps. Brainstorming fires before design. Planning fires before implementation. TDD fires before any production code gets committed. It's structured like a pipeline, not a checklist you can ignore.


The Skills Library

Superpowers ships with skills across three categories:

Testing

  • test-driven-development β€” RED-GREEN-REFACTOR cycle. Includes anti-pattern reference. Code written before tests gets deleted.

Debugging

  • systematic-debugging β€” 4-phase root cause process. No more "try changing this random thing."
  • verification-before-completion β€” Prove it's fixed, don't assume.

Collaboration / Planning

  • brainstorming β€” Socratic design refinement before any code
  • writing-plans β€” Granular tasks, not vague milestones
  • executing-plans β€” Batch execution with human checkpoints
  • dispatching-parallel-agents β€” Concurrent subagent workflows
  • requesting-code-review / receiving-code-review β€” Pre/post review workflow
  • using-git-worktrees β€” Parallel dev branches, isolated environments
  • finishing-a-development-branch β€” Merge decision workflow
  • subagent-driven-development β€” Fast iteration with two-stage review

Meta

  • writing-skills β€” Create your own skills following best practices
  • using-superpowers β€” Intro guide for new sessions

Installation

Claude Code (Official Marketplace)

/plugin install superpowers@claude-plugins-official

Claude Code (via custom marketplace)

/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace

Cursor Agent

/add-plugin superpowers

Or search "superpowers" in the plugin marketplace inside Cursor.

Codex

Tell the agent:

Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.codex/INSTALL.md

OpenCode

Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.opencode/INSTALL.md

Gemini CLI

gemini extensions install https://github.com/obra/superpowers

Verify

Start a new session and prompt:

"help me plan this feature"

If the agent invokes brainstorming instead of writing code immediately β€” it's working.


Before vs After: The Actual Difference

❌ Without Superpowers
──────────────────────
You: "add payment integration"
Agent: [writes 600 lines of Stripe code]
You: "wait, we use PayOS"
Agent: [rewrites 600 lines]
You: "also needs refund flow"
Agent: [adds more untested code]
3 hours later: works in dev, breaks in prod

βœ… With Superpowers
──────────────────────
You: "add payment integration"
Agent: "Which provider? What flows? Edge cases?"
You: [answers]
Agent: [shows design doc, waits for approval]
Agent: [creates git worktree on new branch]
Agent: [writes 8 tasks, 2-5 min each]
Agent: [subagent executes Task 1, writes test first]
Agent: [review: spec βœ“, quality βœ“]
Agent: [continues to Task 2...]
3 hours later: works in dev, works in prod, has tests

What This Means for Teams Using Cursor Enterprise

If your team is already running Cursor Enterprise with Claude models, Superpowers is a low-effort force multiplier. Instead of each developer prompting the agent differently and getting wildly inconsistent results, every session starts from the same structured baseline: spec β†’ plan β†’ TDD β†’ review.

The skills are also extensible. You can write custom skills for your domain β€” think optimizely-content-creation, azure-devops-task-sync, or etm-timesheet-logging β€” and the agent will pick them up automatically. The writing-skills skill ships with a testing methodology to validate your custom skills before committing them to the team.


Verdict

Superpowers solves the right problem. The bottleneck in AI-assisted development isn't speed β€” agents are already fast enough. The bottleneck is alignment: does the agent understand what you actually want before it starts building?

Forcing a brainstorming β†’ planning β†’ TDD loop before every task adds maybe 10 minutes upfront and saves hours of rework downstream. For any team doing serious development with Claude Code or Cursor, this is worth installing.

152k stars and 13k forks as of April 2026. The community clearly agrees.

β†’ github.com/obra/superpowers

← Quay lαΊ‘i Blog