Home / Directory / Superpowers
Superpowers: a skills plugin that argues for process first
Superpowers is a plugin, not a stack pack. Installed, it tries to change how the agent works on any repo: questions first, tests first, evidence before "done."
What it does
The Claude Code install path is the official marketplace (/plugin install superpowers@claude-plugins-official) or the Superpowers marketplace. Other harnesses have their own install notes in the README.
Skills cover brainstorming, git worktrees, writing plans, subagent-driven development, test-driven development, code review and finishing a branch. The README presents these as a workflow, not a menu of optional tips. The agent is supposed to check for a relevant skill before it starts a task.
That is a methodology in plugin form. It does not ship Next.js RLS rules or a FastAPI Alembic checklist. It ships behavior.
Who it is for
Teams that already believe in TDD and written plans and want the agent to share those habits. Also solo developers who keep watching Claude skip the test run.
A bad fit for a three-hour prototype, a design jam, or a repo with no test runner. The plugin will spend your time on process you may not want yet.
Our take
The honest strength is that it attacks a real failure mode: agents that start editing before they know the task, then declare victory without running anything. Forcing a plan and a failing test is a legitimate fix.
The honest limit is friction. Brainstorming and design docs are token-heavy. TDD on a brownfield module can stall. Skills that activate "before any creative work" will annoy you if you asked for a one-line rename.
We use some of these ideas in our own guides (plan first, verify before done). We would not install the whole plugin on every client repo without talking about it first.
Compared with AgentKit Drawer
Our Claude Code Kit is smaller and stack-shaped: subagents with least privilege, hooks that block rm -rf and .env reads, a Stop hook that can run tests. Superpowers is more ambitious about process and less specific about your framework.
If you want methodology, start with Superpowers and keep a short CLAUDE.md for project facts. If you want files that name your commands and your never-dos, start with the kit. They overlap on "don't say done without tests," and that overlap is fine.
Related AgentKit pack
A small Claude Code setup: CLAUDE.md, 6 least-privilege subagents, 10 slash commands, settings.json permissions and 4 hooks. Stack-specific, not a marketplace.
One-time payment · instant download · 14-day refund. We do not claim this third-party kit is affiliated with AgentKit Drawer.