superpowers

Superpowers

Fork Note: This is a fork of obra/superpowers, tuned for fire-and-forget autonomous workflows with AgenC. Changes:

• Edge case discovery: New skill that systematically enumerates failure modes, boundary conditions, and adversarial inputs between architecture approval and error handling design. Includes domain-specific checklists for CLIs, web APIs, frontends, data pipelines, and infrastructure. Integrated as a required step in the brainstorming flow.
• Worktrees disabled: The using-git-worktrees skill is a no-op, and worktree requirements have been removed from subagent-driven-development, executing-plans, and finishing-a-development-branch. All work happens directly on the current branch. See upstream issue #583.
• Batched brainstorming questions: Questions are asked in focused batches as plain text instead of one-at-a-time via the AskUserQuestion tool.
• Three-phase design review: Architecture + components, then edge case discovery, then data flow + error handling + testing — instead of five separate approval rounds.
• Always subagent-driven: The writing-plans skill skips the execution choice and always proceeds with subagent-driven development.

To stay current with upstream: git fetch upstream && git merge upstream/main.

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

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

Note: Installation differs by platform. Claude Code or Cursor have built-in plugin marketplaces. Codex and OpenCode require manual setup.

Claude Code (via Plugin Marketplace)

In Claude Code, register the marketplace first:

/plugin marketplace add obra/superpowers-marketplace

Then install the plugin from this marketplace:

/plugin install superpowers@superpowers-marketplace

Cursor (via Plugin Marketplace)

In Cursor Agent chat, install from marketplace:

/plugin-add superpowers

Codex

Tell Codex:

Fetch and follow instructions from https://raw.githubusercontent.com/obra/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/obra/superpowers/refs/heads/main/.opencode/INSTALL.md

Detailed docs: docs/README.opencode.md

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