superpowers-claude

Superpowers (Claude Code Fork)

Fork of obra/superpowers — stripped to Claude Code only. Upstream version: v4.3.1. For Cursor, Codex, or OpenCode support, use the original.

한국어

Superpowers is a complete software development workflow for Claude Code, built on top of a set of composable "skills" and some initial instructions that make sure your agent uses them.

What's different in this fork

This fork is specialized for Claude Code-only use with the following changes:

Removed (Claude Code only)

• Cursor plugin (.cursor-plugin/), Codex support (.codex/), OpenCode plugin (.opencode/) — all non-Claude platforms removed
• lib/skills-core.js (OpenCode shared module), platform-specific docs and test suites
• SessionStart hook simplified — removed Cursor additional_context field

Added

• dynamic-model-selection skill — routes subagent tasks to the right model tier (opus/sonnet/haiku) based on complexity, reducing cost ~40% while keeping quality where it matters
• GitHub Actions release workflow — tag-push triggers automated GitHub Release from RELEASE-NOTES.md

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 Claude to be able 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.

Installation

In Claude Code:

/plugin marketplace add KyongSik-Yoon/superpowers-claude
/plugin install superpowers-claude@superpowers-claude

Verify Installation

Start a new session and ask for something that should trigger a skill (for example, "help me plan this feature" or "let's debug this issue"). The agent should automatically invoke the relevant superpowers skill.

The Basic Workflow

1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

3. 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.

4. 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.

5. 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.

6. requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

7. 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