Superpowers
Fits agentic coding teams that want brainstorming, planning, testing, debugging, and review enforced as a workflow. It is a poor fit for occasional lightweight skill use or teams unwilling to accept process constraints.
Last push 2026-08-19
- Teams using coding agents such as Codex, Claude Code, or Copilot CLI
- Projects standardizing requirements, TDD, debugging, and delivery
- Users willing to evaluate an opinionated workflow in a non-critical repository
- Users needing only one standalone PDF, spreadsheet, or content skill
- Organizations with a fixed SDLC that forbids third-party workflow intervention
Adoption and exit evidence
A repository is a dependency decision, not only a download.
The README lists Codex App, Codex CLI, Claude Code, Copilot CLI, Cursor, OpenCode, and other hosts, each with a different installation path.
Use the host-specific marketplace or repository instructions. Do not reuse an installation command intended for another client.
Uninstall through the host's plugin manager, then check project files, personal configuration, hooks, and caches for residual state.
Its methodology influences planning, testing, subtasking, and delivery. Actual file and command permissions are inherited from the host agent.
The repository was active, unarchived, and publishing releases on the observation date. High activity does not replace fit testing in your workflow.
The main repository uses MIT. Marketplace terms, third-party dependencies, and referenced resources still require review.
What can go wrong after installation?
This is an opinionated development methodology, not one prompt. Risks include workflow conflict, excessive host-agent permissions, and optional visual-companion telemetry that may need disabling for privacy.
Evidence statusThe README, installation matrix, MIT license, releases, Codex plugin manifest, and telemetry disclosure were reviewed. ToolPickly has not enabled the complete workflow in its production repository.
Run this controlled pilot
Do not use production credentials or sensitive customer data.
- 01
Use a small feature on a temporary branch with no secrets or production data
- 02
Measure effects on completion time, rework, and test coverage
- 03
Confirm telemetry settings satisfy team policy
- 04
After uninstalling, run existing tests and confirm the project does not depend on plugin state
Alternatives by decision
Better for studying or installing individual task skills.
Better for browsing many community extensions before choosing one.
If the team already has a stable review, test, and release process, keeping it may be better than adding another framework.
Official sources and disclosure
Stars are a dated attention signal. They do not determine the verdict. ToolPickly reviewed public repository documentation and clearly identifies what has not been sandbox-tested.
- Superpowers repository ↗
- Superpowers releases ↗
- Superpowers MIT license ↗
- Superpowers Codex plugin manifest ↗
- GitHub repository metadata ↗