superpowers

Superpowers

中文说明: README.zh-CN.md

This is a fork of obra/superpowers.

Fork goals:

• Use this repository as the primary manual install and support source for fork users
• Keep the workflow lighter by removing mandatory worktree and branch-finishing steps
• Treat TDD as opt-in instead of mandatory by default
• Keep brainstorming in the terminal unless the user explicitly asks for browser visuals

Superpowers is a complete software development workflow 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, and no project context to follow. It emphasizes 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.

Sponsorship

If Superpowers has helped you do stuff that makes money and you are so inclined, I'd greatly appreciate it if you'd consider sponsoring my opensource work.

Thanks!

• Jesse

Installation

This fork keeps git-based install docs as the primary path, and it also includes a local Claude Code dev marketplace manifest for testing this checkout.

Claude Code (local dev marketplace)

For local Claude Code development, this repository ships .claude-plugin/marketplace.json so the checkout can be enabled as superpowers@superpowers-dev.

Enable it in ~/.claude/settings.json:

{
  "enabledPlugins": {
    "superpowers@superpowers-dev": true
  }
}

This is for local testing of this git checkout, not a published fork-specific marketplace listing.

Codex

Tell Codex:

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

Detailed docs: docs/README.codex.md

OpenCode

Tell OpenCode:

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

Detailed docs: docs/README.opencode.md

Gemini CLI

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

To update:

gemini extensions update superpowers

Verify Installation

Start a new session in your chosen platform 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, and keeps the default flow in the terminal unless the user explicitly asks for browser-based visuals. Saves design document.

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

3. subagent-driven-development or executing-plans - Activates with plan. Dispatches a fresh subagent per task with two-stage review (spec compliance, then code quality), or executes task-by-task in the current session when subagents are unavailable.

4. test-driven-development (optional) - Activates when the user explicitly asks for test-first work or stronger coverage.

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

The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.

What's Inside

Skills Library

Testing (optional)

• test-driven-development - RED-GREEN-REFACTOR cycle when explicitly requested (includes testing anti-patterns reference)

Debugging

• systematic-debugging - 4-phase root cause process (includes root-cause-tracing, defense-in-depth, condition-based-waiting techniques)