curl -fsSL https://api.cheatcodehq.com/install.sh | sh -s -- superpowers --to allCopies 15 skills into each app's skills folder (Claude Code: ~/.claude/skills), after checking every file against obra/superpowers at commit 8ca22db. Nothing else on your computer changes. To undo it, run the terminal command with --uninstall at the end; that also removes what the app added.
Then start a new session in your AI app and ask for the work in plain words; it picks the skill from its description. In Claude Code you can also type /superpowers:brainstorming.
See it in use
After installing, start a new session and say: Turn spec.md into an implementation plan a developer can follow step by step, point out what the spec leaves open, and save it as plan.md.
What else it can do, and its limits
- 15 skills that give an AI coding agent a working method: brainstorm a design, write a plan, then build it test first
- Debugging that finds the root cause before any fix, and a check that work really passes before it is called done
- Asking for and answering code review, and finishing a branch when the work is complete
- Running plans through helper agents in parallel, writing new skills of your own, and finding out why a session went wrong
- Building, testing and committing need a terminal and git; on files alone it plans, reviews and reasons
Sample input Recorded Oct 24, 2026 in Claude Code 2.1.308 with Sonnet 5.5. The video replays that session; nothing in it was acted or edited.
What's inside 15 skills
brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
diagnosing-superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
Use when executing implementation plans with independent tasks in the current session
Show all 15 skills
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment
Use when creating new skills, editing existing skills, or verifying skills work before deployment
About
An agentic skills framework & software development methodology that works. Disclosure: the brainstorming visual companion loads its logo from primeradiant.com with the version in the URL, which lets the author count use. The upstream README documents environment variables that turn it off.
Something wrong with this listing, or it did not install? Tell us