Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsInstall Superpowers through the instructions for your specific coding-agent harness, then start a fresh session and give it a small coding task. The project’s intended workflow is to clarify the request, present a design for approval, plan the work, and then implement and review it. Superpowers is installed separately in each harness you use.
Install Superpowers in your coding-agent harness
Use the current installation instructions for the exact host you use. Superpowers lists multiple supported harnesses, but setup methods differ and can change. The commands below are examples from the project’s official README, not a universal installer.
As an Amazon Associate I earn from qualifying purchases.
| Harness | Documented installation route |
|---|---|
| Claude Code | Run /plugin install superpowers@claude-plugins-official. The project also documents a separate Superpowers marketplace route. |
| Codex App | Open Plugins in the sidebar, find Superpowers in the Coding section, select +, and follow the prompts. |
| Codex CLI | Run /plugins, search for superpowers, and select Install Plugin. |
| Cursor | In Agent chat, run /add-plugin superpowers, or search the plugin marketplace. |
| Gemini CLI | Run gemini extensions install https://github.com/obra/superpowers. |
| OpenCode | Follow the current instructions in the repository’s .opencode/INSTALL.md. |
| Pi | Run pi install git:github.com/obra/superpowers. |
The README also names Antigravity, Devin CLI, Factory Droid, GitHub Copilot CLI, Grok Build CLI, Kimi Code, Qwen Code, Hermes Agent, and Muse among supported harnesses. For their current setup steps—and any host not listed above—consult the README rather than adapting another host’s command. If you use more than one harness, install Superpowers separately in each.
Free tools Windows power users keep installed
One-click scans. No signup required.
What workflow does Superpowers describe?
Superpowers describes itself as “a complete software development methodology for your coding agents, built on top of a set of composable skills and some initial instructions that make sure your agent uses them.” Its README says relevant skills trigger automatically. The intended process moves from understanding the request to design, implementation, and review:
#1 Best Overall
- Brainstorming: The agent asks questions, explores alternatives, and presents a design in sections for your approval before coding.
- Worktree setup: After approval, it creates an isolated workspace on a new branch, sets up the project, and checks that the test baseline is clean.
- Planning: It breaks the approved design into small tasks, including paths and verification steps.
- Implementation: The project describes two approaches: delegate tasks to subagents and review each task, or execute the plan inline and review at the end of the branch.
- Test-driven development: The documented cycle starts with a failing test, adds the minimum implementation needed to pass, then refactors.
- Code review: The agent checks the work against the plan and reports issues by severity.
- Finishing: It verifies tests, offers choices such as merging, opening a pull request, keeping or discarding the work, and cleans up the worktree.
This is the project’s intended methodology, not a guarantee that every harness or agent will behave identically. Whether a skill activates and how a host handles approvals or worktrees can depend on that host’s integration.
Try a small task after installation
The README says skills trigger automatically, but it does not prescribe one first prompt or verification procedure for every harness. The following is an informal practical check inferred from the documented workflow, not an official cross-harness test or a reported hands-on result.
- Start a fresh session in the harness where you installed Superpowers.
- Give the agent a small, bounded coding goal in a project where you can review the changes.
- Before it edits code, check whether it asks clarifying questions and proposes a design for your approval.
- If it proceeds without the expected steps, check the host-specific installation instructions and whether the harness requires a new session, explicit approval, or another setup step. Avoid assuming the same trigger behavior across hosts.
The project provides a more specific installation-verification example for Muse, but that procedure is Muse-specific; it is not a general test for all supported harnesses.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Updates, license, and optional telemetry
Update behavior depends on the host. The README says updates are “often automatic,” while some integrations have explicit update commands. For example, it documents gemini extensions update superpowers for Gemini CLI. Check the current instructions for your harness before updating.
The project identifies Superpowers as MIT licensed. It also says an optional visual companion loads a Prime Radiant logo and includes the Superpowers version, but not project, prompt, or coding-agent details. The README documents SUPERPOWERS_DISABLE_TELEMETRY as a switch to disable this feature and says Claude Code telemetry opt-outs are honored. These are statements from the project documentation, not an independent audit.
The README mentions enterprise commercial support, additional tooling, or managed spending through Prime Radiant’s sales contact; it does not state prices or service terms.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
