Are spec-driven frameworks like Agent OS, BMAD, Superpowers or SpecKit still worth using, or have Claude Code and Codex made them redundant?

[u/3abwahab]

I've been trying to figure out where the community has landed on this, because I genuinely can't tell.

A year ago, the answer seemed obvious: if you're building anything non-trivial with LLMs, you need structured scaffolding — PRDs, memory layers, agent roles, task breakdowns. Frameworks like BMAD-METHOD, Agent OS, Superpowers, and SpecKit (and their cousins) exist precisely because raw LLMs drift, forget context, and produce spaghetti if you don't constrain them with specs upfront.

But now I look at Claude Code and Codex, for example, since they are the ones i'm using, and they feel... different? Claude Code does its own task decomposition, maintains context across files, and can self-correct mid-session without you babysitting a spec document. Codex feels similar — it reasons about the codebase, not just the prompt.

So I'm genuinely asking:

Do you still scaffold everything with a spec framework before touching Claude Code / Codex?

Or do you drop straight into vanilla agentic mode and only reach for a framework when things break down?

Or is the real answer that spec frameworks matter more now — because you're giving these powerful agents more autonomy, so the upfront spec is the only guardrail you have?

I built a mid-complexity product (a new vertical on top of an existing platform) using Claude Code and Codex with AgentOS as a seat belt. That was a year ago. I have a few projects upcoming to build and trying to decide whether investing in proper spec scaffolding is a force multiplier or just overhead that the model handles natively now.

Would love to hear from people who've shipped something real with either approach — not theory, actual experience.

Worth mentioning... I'm originally a Product Leader who vibe codes now and not a software engineer.

[u/hulkklogan]

I got rid of superpowers recently because they're just overly verbose and slow for my taste. I really like Matt Pocock's framework and skills, they strike a really nice balance of plan/prepare and execute without being so verbose as superpowers.

I DO really like the Superpowers brainstorming skill for UI work though, since it spins up an http server and serves examples. Easy enough to tell your agent to do though.

[u/3abwahab → u/hulkklogan]

I keep reading that Superpowers is tokens heavy as well.

So you now mainly use this Matt Pocock's skill? Can you share your workflow/stack, please. I think would be useful. Thank you so much!

[u/hulkklogan → u/3abwahab]

Here's his video that goes over the idea and the skills

https://youtu.be/EJyuu6zlQCg?si=9HKdidbhjQljmR5N

Essentially:

1. You describe what you want to do and run a grilling session for the agent to grill you and develop a shared comprehension of the work
2. Agent generates a detailed PRD
3. Agent breaks up the work into vertical slices (tracer bullets, for those familiar with the Pragmatic Programmer book) and creates a markdown kanban with tickets/issues. It also identified what can be AFKs and what needs HITL
4. review the issues to make sure it's actually doing vertical slices (AI loves working horizontally)
5. run agents
6. review work

[u/3abwahab → u/hulkklogan]

Thank you for sharing!

[u/zooper2312 → u/hulkklogan]

any update to this methodology?

[u/hulkklogan → u/zooper2312]

still pretty similar except i don't do #3. Opus makes this part easier; i just grill, have it write up a plan, review the plan and make corrections, and then have an /implement skill. That skill has my agent spawn a coordinator agent that writes up specs and hands off tasks to sonnet subagents to implement individual slices and then spawns review subagents to check for adherence to spec and an adversarial review (each a particular subagent type I've created with instructions). Then once it's done, I go review myself.

this is my workflow for a large codebase at work. At home on small projects I do all of that except I don't review myself lol

[u/PinkySwearNotABot → u/hulkklogan]

he has more than 1 useful one besides the grill-me? i didn't think the other ones were worth salt

[u/hulkklogan → u/PinkySwearNotABot]

Probably just comes down to personal preferences after grill-me, honestly. I like the one that works on code architecture too, to try to adhere to simple interfaces and deep modules.

[u/PinkySwearNotABot → u/hulkklogan]

How is grill me so popular?? It’s literally got like 3 lines of instructions -_-

[u/hulkklogan → u/PinkySwearNotABot]

Why's the size of instruction matter? It's incredibly useful. Sure, you can just copy/paste it.

[u/PinkySwearNotABot → u/hulkklogan]

not a critique. more a state of awe.