superpowers-plan — Claude Code skill: what it does, how to install
superpowers-plan makes the agent draft an implementation plan with small steps, the files each step touches, and a check for every one. Useful before edits that span several files.
MIT 1 installs ★ 852 updated 2026-01-18
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a claude-codeWhat superpowers-plan does
The skill turns on ahead of multi-file work and anything that shifts behavior, data, auth or production workflows. A plan comes first, code second. Debugging that needs the failure pinned down methodically starts the same way.
The plan has a fixed shape: goal, assumptions, numbered steps, risks with mitigations, rollback. Every step names file paths, gives one or two change bullets, and a command that proves it worked. The skill recommends steps of 2–10 minutes and incremental delivery instead of one sweeping edit. Its own rule is blunt: a step with no verification does not pass, so how you confirm the result and how you undo it gets settled before a file is touched.
You get a single SKILL.md holding the rules and the plan template. It installs into Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode, each with its own path.
What it helps with
- split a multi-file edit into steps you can verify
- list the files a change will touch before coding
- work out a rollback before anything breaks
- isolate a bug through step-by-step debugging
- write down the assumptions a plan rests on
Example prompts for the agent
- Draft a plan for the
auth/refactor: steps, files, and a verify command for each - Before touching the schema, lay out the goal, the risks and the rollback
- Break this refactor into small steps, each with a check I can run
How to install superpowers-plan
1Skills CLI (Vercel)
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a claude-code2Manually: put the files in place
~/.claude/skills/superpowers-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/superpowers-plan/
1Skills CLI (Vercel)
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a codex2Manually: put the files in place
.agents/skills/superpowers-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a cursor2Manually: put the files in place
.cursor/skills/superpowers-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthonylee991/gemini-superpowers-antigravity .agent/skills/superpowers-plan2Manually: put the files in place
.github/skills/superpowers-plan/SKILL.md1Skills CLI (Vercel)
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthonylee991/gemini-superpowers-antigravity --path .agent/skills/superpowers-planManually: put the files in place
.devin/skills/superpowers-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about superpowers-plan
How do I install superpowers-plan in Claude Code?
Run npx skills add anthonylee991/gemini-superpowers-antigravity --skill superpowers-plan -a claude-code. The skill ends up at ~/.claude/skills/superpowers-plan/SKILL.md.
What does superpowers-plan do?
It has the agent write a plan before non-trivial edits: goal, assumptions, small steps with files and checks, risks, rollback.
Which changes call for this skill?
Edits across several files, anything altering behavior, data, auth, billing or production workflows, and debugging that needs the cause narrowed down systematically.
Source text
SKILL.md · MIT
--- name: superpowers-plan description: Writes an implementation plan with small steps, exact files to touch, and verification commands. Use before making non-trivial changes. --- # Planning Skill ## When to use this skill - any multi-file change - any change that impacts behavior, data, auth, billing, or production workflows - any debugging that needs systematic isolation ## Planning rules - Steps should be **small** (2–10 minutes each). - Every step must include **verification**. - Prefer **incremental deliverables** (avoid “big bang” edits). - Identify **rollback** and **risk controls** early. ## Plan format (use this exact structure) ### Goal ### Assumptions ### Plan 1. Step name - Files: `path/to/file.ext`, `...` - Change: (1–2 bullets) - Verify: (exact commands or checks) 2. ... ### Risks & mitigations ### Rollback plan
© anthonylee991 · MIT · anthonylee991/gemini-superpowers-antigravity