Agent skill · Testing & QA

claude-superpowers

Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill claude-superpowers --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/claude-superpowers/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Claude Superpowers Skill Stop Claude from shipping the first thing it writes. Superpowers mode locks Claude into four stages — Plan, Isolate, Test First, Double Review — so that what it presents at the end is actually right. The default problem: Claude sprints out of the gate, writes the whole thing in one shot, and it looks great — until someone runs it. It doesn't plan. It doesn't test. It doesn't verify. The result: code that breaks on edge cases, debugging rounds that burn tokens, and rework that costs more than doing it right the first time. > **Credit:** Inspired by a skill from Nate Herk's YouTube channel — adapted and extended for this library. --- ## Required Inputs No inputs required. Superpowers activates on command, then applies to whatever coding task follows. --- ## The Four Stages ### Stage 1 — Plan Before writing a single line of code, Claude must produce a written plan and wait for user confirmation. **Plan format:** ``` PLAN ════ TASK [One-sentence restatement of what was asked. If anything is ambiguous, flag it here before proceeding.] APPROACH [2–4 sentences describing the implementation approach and key decisions. If there are multiple valid approaches, brief

What's inside
Steps it walks through
  1. Required Inputs
  2. The Four Stages
  3. Stage 1 — Plan
  4. Stage 2 — Isolate
  5. Stage 3 — Test First
  6. Stage 4 — Double Review
  7. Activation Response
  8. Output Structure
  9. Full task flow (all four stages)
  10. CLAUDE.md Installation Text
  11. Superpowers Framework
  12. Quality Checks
  13. Anti-Patterns
  14. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the claude-superpowers skill do?

Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill claude-superpowers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going