Superpowers in 2026: Still Worth It After Fable 5?

TL;DR

• The methodology survives. The monolith doesn’t. Brainstorm → plan → implement with verification is still the highest-leverage habit in agentic coding. Installing all of it as one always-on harness is no longer the obvious default.
• The community is split, not done. The thread that prompted this post has people abandoning it, people forking it, and an OP who turned it off — then turned it back on the same day.
• The top-voted criticism is “bloated,” not “wrong.” Nobody serious disputes the workflow. They dispute paying tokens for harness on models that plan competently unprompted.
• Fable 5 shrinks the gap but doesn’t close it. Early reports say Fable needs less scaffolding — and at double Opus pricing, harness tokens cost double too. But the heaviest Superpowers users are forking it for orchestration, not deleting it.
• Our call: teams and newer Claude Code users should install the full plugin. Experienced solo developers should cherry-pick modules — start with brainstorm and plan — and let the model handle the rest.

What Superpowers actually is (for anyone joining late)

Superpowers is an MIT-licensed skills framework — a set of markdown instruction files agents must follow — that turns a coding agent into a disciplined engineering process. Jesse Vincent (GitHub: obra, of Request Tracker and Keyboardio fame) published it on October 9, 2025, with a blog post whose thesis fits in one line: “Skills are what give your agents Superpowers.” The repo describes itself as “an agentic skills framework & software development methodology that works,” and it became one of the most-starred projects in the Claude Code ecosystem within months.

The pitch, per the README: when you start building something, the agent doesn’t jump into code. It teases a spec out of you, shows it “in chunks short enough to actually read,” writes an implementation plan “clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing,” then runs subagent-driven development — worker agents executing plan steps with review between each. The current skill set, straight from the repo:

skills/
├── brainstorming
├── dispatching-parallel-agents
├── executing-plans
├── finishing-a-development-branch
├── receiving-code-review
├── requesting-code-review
├── subagent-driven-development
├── systematic-debugging
├── test-driven-development
├── using-git-worktrees
├── using-superpowers
├── verification-before-completion
├── writing-plans
└── writing-skills

Two facts matter for the “is it dead” question. First, it is not abandoned: the repo had commits this week, and Superpowers 5 shipped in March 2026 with visual brainstorming (HTML mockups in a browser instead of ASCII art), an adversarial spec-review loop, and subagent-driven development as the default — with workers explicitly routed to cheaper models. Second, it outgrew Claude: the README now documents installs for Codex CLI, Gemini CLI, Cursor, OpenCode, Factory Droid, and GitHub Copilot CLI. Superpowers stopped being a Claude Code plugin and became a portable methodology.

There’s a third fact worth savoring. Three days after launch, when Anthropic shipped native skills support, Vincent himself published “Superpowers 2.0 came out yesterday and might already be obsolete” — concluding, about his hand-rolled bootstrap mechanism, “I’m low-key excited that I might not have to maintain that going forward.” The project has been racing native features since week one. That race is the whole story of this post.

The ten modules: the à-la-carte version of the methodology

Obra’s plugin installs the methodology as one unit. MCP.Directory’s skills catalog lists a different shape: ten standalone superpowers-* skills — community ports of the methodology (primarily anthonylee991’s adaptation, plus one lab environment from sickn33) broken into single-purpose modules you can install one at a time. To be clear: these are not obra’s original files. They are the same workflow ideas, repackaged so you can adopt the 20% you’ll actually use. Here’s the map:

The interesting design decision in the ports: the Python and REST automation modules don’t exist in obra’s core at all. The community took the workflow scaffolding and attached domain playbooks to it. That’s the skills-as-process-knowledge thesis working exactly as Vincent described it.

The case for: forced sequencing still wins

Strip away the branding and Superpowers does one thing: it makes the agent earn the right to write code. Every credible positive report traces back to that sequencing, not to any magic prompt. Evan Schwartz’s April 2026 review — which pulled 50 points and a real argument on Hacker News — is the cleanest articulation:

The same shape shows up in the r/ClaudeCode thread that prompted this post. The argument for keeping it isn’t “the model can’t code” — it’s confidence and reviewability:

Three more pro-arguments from the thread hold up under scrutiny. Consistency: “having harnesses makes the output more consistent especially for larger projects — also if you switch AI vendors” (u/octopus_limbs) — and vendor portability is now a documented feature, not a hope. The brainstorming front-end: several commenters use only the brainstorm phase, including the Superpowers 5 visual mode that pops a local web server and Playwright so you approve mockups in a browser instead of squinting at ASCII. And the OP’s own behavior is the most honest data point in the thread: turned it off, missed it, turned it back on within a day.

Takeaway: the durable value is the forced pause between intent and implementation, plus the artifacts (specs, plans) it leaves behind. That value is real and model-independent.

The case against: harness tax on models that don’t need a harness

Now the other side, and it’s not a strawman — it’s the single most-upvoted comment in the thread:

Read that carefully, because it’s the entire 2026 debate in three sentences. The criticism concedes the methodology and rejects the packaging. Four concrete charges stick:

• Token cost is by design, not accident. Structured brainstorms, multi-page specs, adversarial spec review, and subagent dispatch all spend tokens before line one of code. Vincent’s own Superpowers 5 notes flag visual brainstorming as “token-intensive.” On a rationed Pro window, running the full loop on a one-file fix is malpractice.
• Native features keep eating the bottom of the stack. Plan mode, native skills, the official plugin marketplace, and built-in subagents now cover ground Superpowers had to invent in 2025. One thread commenter (u/ThreeKiloZero) runs “lean with core rules and skills” plus hooks for steering, arguing skills “aren’t being updated to leverage all the new prompting styles that are model-specific.” If you’re unsure which primitive owns which job, our skills vs MCP vs subagents decision matrix draws those boundaries.
• Some users report it makes output worse. From the HN thread on Schwartz’s review: “I personally don’t like superpowers very much… I think Claude makes more mistakes when using superpowers than when not” (d--b). A minority view, but it exists and deserves the link.
• Even the author tells you to override it. Superpowers 5’s guidance, verbatim: “prefer direct instructions from you, your CLAUDE.md or your AGENTS.md to Superpowers internal instructions.” When the framework’s own release notes demote the framework below your project config, “install everything and trust it” is no longer the author-endorsed posture.

One more contrarian note from HN worth keeping in view: skill frameworks are instructions your agent obeys, fetched from the internet — “curl|bash but with added LLM agents,” as one commenter put it. MIT license and a readable repo mitigate that for Superpowers specifically; the habit of auditing what a skill tells your agent to do should survive anyway.

Takeaway: nobody has refuted the workflow. The case against is a cost-benefit case, and on 2026 models the benefit side shrank while the cost side didn’t.

The Fable 5 question: does a self-verifying model need a discipline harness?

The thread exists because of Fable 5 — the OP asks whether Superpowers is “still needed with the new models and features (like Ultracode).” The model’s documented pitch overlaps Superpowers’ pitch almost line for line: it investigates before acting and verifies its own work with less prompting (see our Fable 5 routing guide for the mechanics). And because Fable launched at double Opus pricing, every token of harness costs twice as much. The economics produced the thread’s bluntest line:

Case closed? No — because the most detailed comment in the thread runs the other way. One heavy user tried Fable 5 bare, then reverted: “I tried Fable 5 without it. Today I am going back to Opus + my superpowers fork for orchestration… Fable isn’t noticeably better than Opus at planning” (u/nickguletskii200), reporting that Fable still “forgets to do things or cuts corners” on big-bang changes. The sophisticated position emerging from the wreckage isn’t “Superpowers or not” — it’s a two-variable problem: which model, and how much harness.

Our read of the early signal, stated as a position you can disagree with: on Fable 5, run thin — the model self-verifies, so keep at most brainstorm and review and let it work. On Opus and Sonnet, the full workflow still pays, especially for multi-hour autonomous runs where drift compounds. And caveat everything: Fable shipped on June 9. This thread is days old. Anyone claiming settled answers is selling something.

Who should still install it in 2026

Five profiles cover almost everyone asking this question. Find yours:

How to install — full plugin or just the modules

The full methodology, from Anthropic’s official plugin marketplace (or Vincent’s own), inside Claude Code:

# Official Claude plugin marketplace
/plugin install superpowers@claude-plugins-official

# Or: Jesse Vincent's own marketplace
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace

The à-la-carte path: browse the ten modular superpowers-* listings in the skills catalog and install only the phases you want enforced. A sane minimal stack, in the order we’d add them:

1. superpowers-brainstorm — the highest-value 20%: options, tradeoffs, acceptance criteria before any code.
2. superpowers-plan — small steps, exact files, verification commands. The artifact Opus-tier models execute well against.
3. superpowers-debug — the one to keep even on Fable: reproduce → isolate → hypothesize beats vibes at any model tier.
4. superpowers-tdd + superpowers-review — if you want enforcement, not just suggestion, of tests-first and severity-ranked review.
5. superpowers-workflow — only if you decide you want the whole loop after all; it chains the others.

One operational warning before you file a bug: skills that never fire are usually a description problem, not a model problem. If your freshly installed module sits silent, work through why your Claude skill isn’t activating first.

What we got wrong

Three assumptions we carried into this research that didn’t survive it:

• We assumed our catalog’s superpowers-* skills were obra’s originals. They’re community ports of the methodology, not mirrors of his files — which turned out to be the more interesting story: the workflow has been unbundled and remixed by people who wanted the discipline without the monolith.
• We expected the thread to read as an obituary. It doesn’t. The OP turned Superpowers back on within a day of disabling it, the harshest critic praised the workflow, and the most technical commenter is forking it rather than dropping it. “Still using it?” threads about genuinely dead tools look nothing like this.
• We assumed Fable 5 settled the harness question. It reopened it. The same week produced “a good way to waste a day of tokens” and “going back to Opus + my superpowers fork.” Model capability changed the price of discipline, not the value of it.

Verdict

Frequently asked questions

Glossary

• Skill — a markdown instruction file (SKILL.md) an agent loads and follows when its description matches the task.
• Superpowers — Jesse Vincent’s MIT-licensed framework of composable skills enforcing a full development methodology.
• Harness — the agent runtime around the model (Claude Code, Codex CLI, Gemini CLI) plus any scaffolding you add to steer it.
• Plugin marketplace — Claude Code’s registry for installing bundles of skills, commands, and hooks (/plugin install …).
• Brainstorm → plan → implement — Superpowers’ core loop: align on intent, write a stepwise plan, only then write code.
• Subagent-driven development — worker agents execute plan steps in fresh contexts while an orchestrator reviews each result.
• TDD (red/green/refactor) — write a failing test, make it pass, then clean up; Superpowers enforces it rather than suggesting it.
• YAGNI — “You Aren’t Gonna Need It”; build only what the spec requires.
• Context bloat — tokens spent on instructions and ceremony instead of task content; the core 2026 criticism of heavy frameworks.
• Fable 5 — Anthropic’s June 2026 flagship; investigates and self-verifies with less prompting, at roughly double Opus pricing.

Sources

Primary

• github.com/obra/superpowers — README, skill list, install paths, license; activity verified June 2026
• blog.fsck.com — Superpowers (Oct 9, 2025) — the original announcement and philosophy
• blog.fsck.com — “Superpowers 2.0… might already be obsolete” (Oct 12, 2025) — Vincent on Anthropic’s native skills
• blog.fsck.com — Superpowers 5 (Mar 9, 2026) — visual brainstorming, spec review loop, “prefer direct instructions from you”

Community

• r/ClaudeCode — “Are you guys still using the superpowers skill?” — the June 2026 thread; all Reddit quotes above
• Hacker News — discussion of the Schwartz review — contrarian takes on mistakes, granularity, and skill supply-chain trust
• emschwartz.me — A Rave Review of Superpowers (Apr 2026) — the strongest independent positive case

Note on tweet embeds: Jesse Vincent no longer posts on X (his account points to Mastodon/Bluesky), so no first-party tweet exists to embed. His announcements live on his blog, linked above.

Internal

• /blog/fable-5-claude-code-model-routing-guide-2026
• /blog/claude-skills-vs-mcp-vs-subagents-vs-cli-2026-decision-matrix
• /blog/why-your-claude-skill-isnt-activating-2026-fixes
• /skills — browse all agent skills
• /clients/claude-code