team.management vs Superpowers.
Superpowers and team.management make the same promise — disciplined AI development — with opposite mechanisms. Superpowers, by its own README, works “not through tool gating but via structured instructions.” team.management is the tool gating.
What Superpowers is
Superpowers is Jesse Vincent’s composable skills framework and full development methodology — brainstorm → plan → TDD → subagent execution → mandatory review — installed as a plugin across Claude Code, Codex, Cursor, Copilot CLI and others. It is the most-starred workflow plugin in the space (≈256k stars, v6.x, as of July 2026) and its TDD discipline in particular is genuinely deep.
Its README states the mechanism plainly: the methodology holds “not through tool gating but via structured instructions.” The skills trigger automatically and tell the model what a disciplined engineer would do next.
What team.management is
team.management is the other mechanism: an open-source protocol engine inside Claude Code where the process lives in a state machine, not in the instructions. A PreToolUse hook checks every tool call against the current protocol step — in discussion mode the edit tools are blocked before they execute. Nothing needs to be remembered, because nothing is being asked. The mechanics are documented in the DAIC loop.
The core difference — asking well vs not asking
Structured instructions work most of the time — the model usually complies, and Superpowers’ results show it. “Usually” is exactly the problem enforcement exists to solve. Instructions compete with everything else in context: a long debugging session, a user in a hurry, an eager model that’s sure it’s right. A PreToolUse hook doesn’t compete for attention. In discussion mode the edit tool comes back blocked — every time, at hour one and at hour eleven.
Could you disable it? Sure — it’s your machine and your config, and the diff would show it. The model doesn’t get that option. That’s the point: you stay free; the agent stays on the rails.
| Superpowers | team.management | |
|---|---|---|
| Mechanism | Skills — structured instructions the model follows | Hooks — runtime gates the model can’t override |
| Own words | “not through tool gating but via structured instructions” | “A hook that runs before the tool, in the runtime — not an instruction in the prompt” |
| Methodology | Brainstorm → plan → TDD → subagent execution → review | Protocols: task, brainstorm, research, refactoring, optimize |
| Process state | In the conversation and skill state | In the engine: step, mode, task file, audit log — outside the context window |
| Git & task automation | Via skills and workflows | Branch per task, task files, status transitions — engine-managed |
| Harness reach | Claude Code, Codex, Cursor, Copilot CLI and more | Claude Code native (Codex/Antigravity join as reviewers) |
| Repository | github.com/obra/superpowers | github.com/TeamManagementPlugin/claude-plugin |
| Price & license | Free, open source | Free, MIT |
Run the skills — on rails
Superpowers’ methodology and skill library are excellent, and skills run happily inside protocol steps: let the brainstorm and TDD skills do what they do best, and let the engine hold the line those skills assume — implementation locked until alignment, review actually happening before “done.” Working solo, with your eyes on the session, Superpowers alone may be all you need. But if you answer for agents you weren’t watching, “the model was instructed to” is not an answer you can give a client. Put the same skills on rails.
FAQ
What is the actual difference between skills and hooks?
A skill is an instruction set the model loads and follows — it improves behavior but the model can still deviate, especially deep into a long session. A hook runs in the harness before each tool call and allows or blocks it by exit code. One shapes the model’s intent; the other constrains its actions regardless of intent.
Is Superpowers’ methodology compatible with team.management?
Largely yes. Superpowers’ brainstorm-plan-TDD-review methodology maps naturally onto team.management’s protocol steps, and skills can run inside protocol steps. If you rely on Superpowers’ multi-agent patterns, check them against DAIC mode gating — subagents get explicit whitelists in team.management.
Which one should a team standardize on?
If you want a rich skill library and multi-harness reach (Claude Code, Codex, Cursor and more), Superpowers is the broader ecosystem. If you need a guarantee that every member’s agent followed the process — not a well-worded request that it do so — only the hook layer can give you that, and that layer is team.management.
Facts and figures on this page are as of July 2026, verified against the sources linked inline. If you’re reading this much later — check the sources.