--- slug: "superpowers-superpowers" source_type: "readme" source_url: "https://cdn.jsdelivr.net/gh/LUNARTECH-X/superpowers@main/README.md" repo: "https://github.com/LUNARTECH-X/superpowers" source_file: "README.md" branch: "main" --- # Superpowers ![Superpowers Banner](https://github.com/LUNARTECH-X/superpowers/raw/HEAD/assets/lunartech-banner-m1.png) 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. ## About Superpowers is built by [LunarTech](https://lunartech.ai/). - [LunarTech on LinkedIn](https://www.linkedin.com/company/lunartechai/) - [Vahe Aslanyan](https://www.linkedin.com/in/vahe-aslanyan/) - [Tatev Karen Aslanyan](https://www.linkedin.com/in/tatev-karen-aslanyan/) ## 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, consider supporting the project. ## 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: ```bash /plugin marketplace add obra/superpowers-marketplace ``` Then install the plugin from this marketplace: ```bash /plugin install superpowers@superpowers-marketplace ``` ### Cursor (via Plugin Marketplace) In Cursor Agent chat, install from marketplace: ```text /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](https://github.com/LUNARTECH-X/superpowers/blob/HEAD/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](https://github.com/LUNARTECH-X/superpowers/blob/HEAD/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. 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 — 1,349 skills The Superpowers skills library has grown well beyond the core development workflow. The full set is enumerated in [CATALOG.md](https://github.com/LUNARTECH-X/superpowers/blob/HEAD/CATALOG.md). High-level breakdown: | Group | Skills | What's inside | |---|---:|---| | Core workflow | 14 | TDD, planning, debugging, code review, worktrees, subagent dispatch | | `writing-and-planning/` | 865 | Copywriting (`document-editorial`, `document-skills`, `writing-skills`), productivity | | `academy-skills/` | 201 | Academic research, paper writing, citations, scientific tooling, 100+ database connectors — curated from 5 upstream repos with duplicates removed and naming standardized | | `data-and-science/` | 151 | Research and data tooling | | `marketing/` | 35 | Branding, campaigns and creative ideation | | `development/` | 34 | Backend, frontend, devops, architecture, git workflows, debugging, database, best practices, code review | | `business/` | 26 | Founder workflows, strategy | | `design-and-media/` | 18 | UI/UX, visuals | | `ai-and-agents/` | 5 | Agent development, orchestration | #### Core workflow skills (the 14 that drive the loop) **Testing & verification** - **test-driven-development** — RED-GREEN-REFACTOR cycle (includes testing anti-patterns reference) - **systematic-debugging** — 4-phase root cause process (root-cause-tracing, defense-in-depth, condition-based-waiting) - **verification-before-completion** — Confirm it's actually fixed before declaring done **Planning & execution** - **brainstorming** — Socratic design refinement - **writing-plans** — Detailed implementation plans - **executing-plans** — Batch execution with checkpoints - **subagent-driven-development** — Fast iteration with two-stage review (spec compliance, then code quality) - **dispatching-parallel-agents** — Concurrent subagent workflows **Branch & review** - **using-git-worktrees** — Parallel development branches - **requesting-code-review** — Pre-review checklist - **receiving-code-review** — Responding to feedback - **finishing-a-development-branch** — Merge/PR decision workflow **Meta** - **writing-skills** — Create new skills following best practices - **using-superpowers** — Introduction to the skills system For the complete listing across all categories — every skill with its path, name, and description — see [CATALOG.md](https://github.com/LUNARTECH-X/superpowers/blob/HEAD/CATALOG.md). ## Philosophy - **Test-Driven Development** - Write tests first, always - **Systematic over ad-hoc** - Process over guessing - **Complexity reduction** - Simplicity as primary goal - **Evidence over claims** - Verify before declaring success Read more about the Superpowers philosophy in the skills documentation. ## Contributing Skills live directly in this repository. To contribute: 1. Fork the repository 2. Create a branch for your skill 3. Follow the `writing-skills` skill for creating and testing new skills 4. Submit a PR See `skills/writing-skills/SKILL.md` for the complete guide. ## Updating Skills update automatically when you update the plugin: ```bash /plugin update superpowers ``` ## License MIT License - see LICENSE file for details ## Support - **Issues**: https://github.com/obra/superpowers/issues - **Marketplace**: https://github.com/obra/superpowers-marketplace