How do I install the Superpowers skill?

Run npx skillmds@latest add heymegabyte/superpowers in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Superpowers safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Superpowers?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Superpowers free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Superpowers?

heymegabyte (@heymegabyte) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Superpowers by heymegabyte — Agent Skill

Name: Superpowers
Author: heymegabyte

File contents

Superpowers — Process Discipline

Vendored from obra/Superpowers (MIT, Jesse Vincent), compressed to house style — see NOTICE.md. These are process skills: they decide HOW to approach a task and run BEFORE implementation skills. On conflict, this repo's 01-operating-system + rules/* + Brian's preferences win.

The flow (route by where you are)

Starting anything creative? → brainstorming/SKILL.md — explore intent + design before code. Non-negotiable first step.
Have requirements, multi-step? → writing-plans/SKILL.md — write the plan before touching code.
Work needs isolation? → using-git-worktrees/SKILL.md — spin an isolated workspace ([[main-only-branch]]).
Executing the plan? → subagent-driven-development/SKILL.md — one subagent per task + two-stage review ([[monitor-orchestration]], [[parallel-subagent-economy]]).
Before merge? → requesting-code-review/SKILL.md — dispatch the code-reviewer agent + Agent Diversity Review ([[agent-selection]]).
Got feedback? → receiving-code-review/SKILL.md — verify it technically, then act; no blind agreement.
Tests green, done? → finishing-a-development-branch/SKILL.md — merge / PR / cleanup ([[no-staging-doctrine]], auto-push).

Authoring a skill itself? → writing-skills/SKILL.md + [[skill-authoring-contract]] (the house authoring rule, where the SDO / match-the-form / ordered-by-weight insights now live).

Agent map

requesting-code-review → the code-reviewer agent + diversity gate.
subagent-driven-development → meta-orchestrator / parallel Agent spawns.
brainstorming → pairs with 14-independent-idea-engine.

Folded — these live in rules/, not duplicated here

test-driven-development → [[e2e-tdd-organization]]
systematic-debugging → [[error-recovery]]
verification-before-completion → [[verification-loop]]
dispatching-parallel-agents → [[parallel-subagent-economy]]
executing-plans → [[monitor-orchestration]]
using-superpowers → 01-operating-system (skill-check before action)
writing-skills best insights (SDO, match-the-form, ordered-by-weight, human-voice) → [[skill-authoring-contract]]

---name: superpowersdescription: Use when starting creative work, planning a multi-step task, isolating a workspace, wrapping a branch, or giving/getting code review. Not when the task is a one-line fix with no design surface.---# Superpowers — Process DisciplineVendored from [obra/Superpowers](https://github.com/obra/Superpowers) (MIT, Jesse Vincent), compressed to house style — see `NOTICE.md`. These are **process skills**: they decide HOW to approach a task and run BEFORE implementation skills. On conflict, this repo's `01-operating-system` + `rules/*` + Brian's preferences win.## The flow (route by where you are)1. **Starting anything creative?** → `brainstorming/SKILL.md` — explore intent + design before code. Non-negotiable first step.2. **Have requirements, multi-step?** → `writing-plans/SKILL.md` — write the plan before touching code.3. **Work needs isolation?** → `using-git-worktrees/SKILL.md` — spin an isolated workspace (`[[main-only-branch]]`).4. **Executing the plan?** → `subagent-driven-development/SKILL.md` — one subagent per task + two-stage review (`[[monitor-orchestration]]`, `[[parallel-subagent-economy]]`).5. **Before merge?** → `requesting-code-review/SKILL.md` — dispatch the `code-reviewer` agent + Agent Diversity Review (`[[agent-selection]]`).6. **Got feedback?** → `receiving-code-review/SKILL.md` — verify it technically, then act; no blind agreement.7. **Tests green, done?** → `finishing-a-development-branch/SKILL.md` — merge / PR / cleanup (`[[no-staging-doctrine]]`, auto-push).**Authoring a skill itself?** → `writing-skills/SKILL.md` + `[[skill-authoring-contract]]` (the house authoring rule, where the SDO / match-the-form / ordered-by-weight insights now live).## Agent map- `requesting-code-review` → the `code-reviewer` agent + diversity gate.- `subagent-driven-development` → `meta-orchestrator` / parallel `Agent` spawns.- `brainstorming` → pairs with `14-independent-idea-engine`.## Folded — these live in rules/, not duplicated here- `test-driven-development` → `[[e2e-tdd-organization]]`- `systematic-debugging` → `[[error-recovery]]`- `verification-before-completion` → `[[verification-loop]]`- `dispatching-parallel-agents` → `[[parallel-subagent-economy]]`- `executing-plans` → `[[monitor-orchestration]]`- `using-superpowers` → `01-operating-system` (skill-check before action)- writing-skills best insights (SDO, match-the-form, ordered-by-weight, human-voice) → `[[skill-authoring-contract]]`

Frequently asked questions

Superpowers