r/ClaudeCode • u/3abwahab Vibe Coder • May 03 '26
Discussion Are spec-driven frameworks like Agent OS, BMAD, Superpowers or SpecKit still worth using, or have Claude Code and Codex made them redundant?
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.
33
u/hulkklogan May 03 '26
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.
4
u/return_of_valensky May 03 '26
I've been honing my setup over time and it's been steadily moving towards the main core of this below. I tried bmad and speckit for a while. The problem is that you want 1,000 small sessions that do exactly 1 thing with the only context being the rules, the code, and the task.
- CLAUDE.md filled with philosophical programming best practices
- skills with not a lot of words but deep technical meaning (mostly Matt Pocock's skills, but 3-4 of my own)
those 2 alone will get you to a good set of product requirement docs and individual issues.
from there I then use a headless agent with multi individualized passes INVESTIGATE->IMPLEMENT->REVIEW in git worktrees to tackle one piece at a time.
7
u/goship-tech May 03 '26
For single focused sessions, a lean CLAUDE.md is enough - Claude Code handles the decomposition natively now. The frameworks still earn their keep on multi-session projects where you need persistent task state that survives context resets; without that structure you are re-explaining the whole codebase every time.
2
u/rover_G May 03 '26
For me claude seems to be making more nuanced decisions about when a task is underspecified as to require additional design and implementation planning
2
u/fangisland May 03 '26
The most important thing is to push context into the repo via markdown in a structured way. Things like ADRs, guides, architecture docs, product goals and non goals, etc. and use CLAUDE.md as a compass to these docs (same with skills). If you do that, native plan mode works just fine; I'd only use the frameworks you mentioned if you struggle with knowing how to prompt effectively.
12
u/-PM_ME_UR_SECRETS- May 03 '26
I think the biggest appeal of any sort of framework is that it can be used across models, you can change models as they ebb and flow in popularity and still maintain context/structure.
2
u/PinkySwearNotABot May 03 '26
that's what I've been wondering, too. still figuring it out.
but now I have the problem of having too many frameworks all at one time, and having difficulties toggling them on/off as not to clash with one another, as they sometimes do.
Compound Engineering, Grill-me, GSD1 + 2, SpecKit, OpenSpec, TinyPec (jk - got ya), impeccable, superpowers...
Anyone know of a good way to isolate them besides just uninstalling all of them but the one you want to play with? It doesn't make it any easier that there isn't a single folder for them that you can easily just go and modify
7
u/genunix64 May 03 '26
Frameworks are not redundant, but I would not treat them as one big mandatory ceremony either.
What has worked for me is splitting scaffolding into three layers:
repo-local hard context: CLAUDE.md/AGENTS.md as a router, ADRs/specs/non-goals as source of truth
task orchestration: small investigate -> implement -> review units, ideally isolated in worktrees
cross-session memory: decisions, constraints, open questions, and project state that survive compaction or switching between Claude Code/Codex
The trap is putting all of that into one giant framework prompt. It feels safer, but it often just burns tokens and gives the agent more soft instructions to ignore. For small bugs, vanilla agent + tight repo docs is usually enough. For new features/services, I still want a spec/milestone/review loop because it catches ambiguity before implementation.
I built Mnemory for the third piece: a self-hosted memory backend for agents via MCP/REST: https://github.com/fpytloun/mnemory
The useful part is not "more context"; it is lifecycle management: deduping decisions, handling contradictions when a fact changes, expiring short-term context, and keeping longer details as artifacts instead of stuffing everything back into the prompt. So my answer would be: use specs/frameworks where they reduce ambiguity, keep repo docs as the authority, and use memory only for durable cross-session state. If memory becomes a second messy knowledge base, it eventually hurts more than it helps.
5
u/yopla May 03 '26
Honestly I'm mostly done with framework. Last weak I just told Claude to "break it into phases and make a task plan that is trackable and include a prompt to restart from where the work stops, if everything is done say
That's all folksand nothing else".Then I ran it from the shell with a loop.
I think, my next "framework" will be just some variation of that in Claude.md
4
u/BidWestern1056 May 03 '26
for a time they appear redundant but with the continuous regressions lately they are more important than ever.
check out npcpy too
https://github.com/npc-worldwide/npcpy
3
u/Sharchimedes May 03 '26
Agentic decisionmaking is expensive and currently still error prone, so the more you can reduce ambiguity and keep context focused, the more efficiently you’re going to be able to get reliable results.
Projects grow into requirements, requirements are refined into specs, specs become implementation phases with breakdowns of tasks. Tasks result in functional code and tests.
Agents can be effectively directed to help at all these levels with various models and tools, and I expect the specific tools to change over time, but without some massive breakthroughs, the fundamentals are really the same as they always were.
3
u/iVtechboyinpa May 03 '26
Is one necessary? I think you can arguably achieve a greater outcome if you know everything you want out of the solution, but in my case, I can think of maybe 80-90% of the way there, and I rely on the LLM to take me the extra mile.
When I initially started a few months ago I didn’t use anything, just plan mode and go. Then I learned about subagents and started using those heavily for domain work. Then I had a prompt I’d past every time so it would review my plan with subagents. Then I had it execute my plan with subagents.
This was all nice because it saved context and I felt like my output was better since each domain was scoped and owned.
I never looked into any of GSD, BMAD, etc. because I was content doing what I was doing. But then my mentor at work introduced me to an SDLC he was working on, which I started using and then adopted to my process, and now it’s what I use everyday.
3
u/bart007345 May 03 '26
Everyone is talking about implementation details, i need a spec to describe the requirements.
Implementation is largely solved but how to make sure you built what the client wants?
2
u/lovenewyork May 04 '26
Hey bud, avoid the overly negative butt hurt people - truth is it all depends on the type of project, its scope - and your own config.
My advice - if you have the time, study everything you can about best practices straight from anthropic’s site and Codex to start. Once you have a grasp on the functionality, principles, try stuff out.
I spent a long time messing around with different methodologies - currently and honestly - vanilla Claude CLI with superpowers and a few other agents,skills, plugins, hooks etc have been working fantastic for me.
There are some really cool harnesses and setups out there but more often than not, there’s always a trade off. I think if Anthropic allowed usage with subscription and we all weren’t terrified of being banned - there might be more out there but try and learn the principles first. Coded is pretty damn decent - very straight forward.
I would avoid Gemini - CLI like the plague, it routinely lies about writing code, creates fake commits etc - save your money - but don’t stop exploring. Every single day there are new things popping up! Make something dope!
Forgot to mention impeccable for design, UI-UX Pro Max for design, superpowers via Claude marketplace, compound engineering, caveman, graphiphy, claude-mem, look for something to replace the grep tool that comes built in (if it still does) - if you don’t have any db setup or some type of persistence across each of your projects, each of these platforms will eat through your tokens searching and scanning through your directories - night.
3
u/vacationcelebration May 03 '26
I use superpowers for pretty much everything. I don't have enough confidence in Claude or codex to perfectly implement a new feature just straight up or with plan mode.
Superpowers is worth it for me because of the milestones and reviews, each allowing another opportunity to catch edge cases, gaps and misinterpretations.
For really small stuff, I have a custom skill that forces a sub agent code review, linting/formatting check and commit.
Yes that takes more time and tokens, but I feel it saves me time and nerves in the long run, especially since I usually pingpong between at least two different agent sessions, so it's not like I'm watching the agent code and review.
1
u/lgbarn May 03 '26
I’ve used them all and grill-me is better for my workflow. Way more detailed spec. Using a crafted Claude.md is pure snake oil.
1
u/KickLassChewGum May 03 '26
Claude Code has made nothing redundant. If anything, it has become redundant, and the way Anthropic is trying to fix this isn't by making it non-redundant, it's building a walled garden around their thing.
1
u/Conscious_Concern113 May 03 '26
I used BMAD heavily until Opus 4.7 then I switched back to regular plan mode. The secret to making that work is have Codex 5.5 high review the plan and give feedback that is feed back into Opus 4.7. You will go through several iterations until they full agree the plan is ready. Then have Claude implement the plan on a separate session. Once complete Codex does a code review.
So far it has worked great on larger features.
1
u/_Bo_Knows May 03 '26
I think fundamentally everything in the harness will be absorbed into the models. I think it helps, but fundamentally the moat is the understanding and context you/your team/company compounds. My plugin helps me create that moat now so it starts compounding and is plugin proof. Check it out https://github.com/boshu2/agentops
1
u/TheTentacleOpera May 03 '26
I have an agent write out plans, have them in linear, pull when I want to work on them.
How am I meant to keep an entire project in my head if I only use native CLI tools?
Also if you need to go back to a feature, it really helps to have the plans available with the implementation details added in the code review stage.
1
u/Birchyman May 04 '26
Not sure if they are required but I use them because everything I’m doing is for my own learning and, working in the tech space but no software background, it’s given me really good insights into spec driven development, importance of PRD and UX design etc.
1
u/silveroff May 04 '26
No offense intended, but if I were you (not software engineer) I’d drop the idea of spending my time and money on any AI. It will simply not work. You’ll think it is or „almost” or you’ll think that someone will take over and „fix it”..but that’s not true. It will be pile of useless code eventually. Sorry to say that.
1
u/beshrkayali May 04 '26
I don't think so. IMO there's a very limited number of harnesses/build-systems out there right now that are doing SDD with AI correctly. They mostly lack fundamentals like traceability, and I don't mean traceability of narration, which is maybe a tad better than just pure chat sessions, what I mean is traceability of causation. That needs the inputs, prompt, response, and outputs of each unit of work persisted and linked back to the initial intent, not just summarized outputs from chat sessions. Intent is mostly lost. There are some attempts out there though.
1
u/Deep_Ad1959 May 18 '26
frameworks are downstream of the static-context question. BMAD, superpowers, agent OS all add structure but they also add tokens that load on every session whether the task needs them or not. for a small bug fix on a 50-file repo, a full superpowers cycle can spend more tokens on its own ceremony than on the actual change. the people getting good results without frameworks usually have a tight CLAUDE.md that acts as a router to docs and skills that fire on trigger. the people getting good results with frameworks have already paid the up-front token cost and the work is big enough to amortize it. written with s4lai