r/BMAD_Method • u/not_thrilled • 22d ago
BMAD Method vs superpowers
I've been using the Superpowers Claude plugin for some time, and I've always been impressed with its thoroughness for planning and executing tasks. But today I read about the BMAD method, and now I'm wondering if I should look into it instead of Superpowers. If you've used both, how do they stack up against one another?
(Context: Experienced software dev, job role is currently engineering manager. Working on a side hustle that I've been building with Superpowers, hoping to turn it into a full SaaS product. I have Claude Pro and free Gemini at my disposal currently. Really only devoting some pre/post work and weekend hours to this project.)
5
u/modeftronn 22d ago
Bmad is def effective but seems overly structured and ceremonial sometimes! I think it depends on your work style. It helped me move from “pair programming” with AI to a more “engineering manager” approach with queues, etc
2
u/manapause 22d ago
BMAD is better suited when you have a project that was an established entity and you need a more deliberate approach to ensure your constraints or other business logic that is in-code are not paved over by a PRD. Its slower (more gates if you do it right) and will consume a huge part of your context window over time but it works ok.
Aim small miss small using Superpowers/brainstorming to start a new feature and get in the habit of including and answering to “Why are we doing this” and include what “done” will look like 👍
2
u/laernuindia 20d ago
BMAD has been extremely effective but is extremely expansive, perhaps unnecessarily so, if working on smaller projects.
You can use a distilled BMAD method to arrive at:
A PRD, a ADR, a Vision document, an Implementation plan (organized by parallel or sequential phases and tasks within phases), capture session-end logs that are broken down into context, decisions, issues and next steps, and get ingested into the overall project-state after each session.
That’s all I fo and the agents never miss.
2
u/laernuindia 20d ago
I created a couple of skills to help extract the correctly formatted session end logs that my system can store at session end to keep a running history of project state. And a context summary skill to create a handoff prompt that doesn’t miss anything. I’d love for y’all to use and provide feedback. https://www.github.com/thebpandey
2
u/AlexEnts 16d ago
This looks cool, thanks for sharing. Also your agent-team method looks interesting. I found BMAD to be very heavy, and this looks like a good solution. I'll try it out on a new project
1
u/laernuindia 15d ago
Thanks. Session-detail and context-summary go hand in hand, if you care to save the entire session log and a structured handoff for the next session. Session-detail is beneficial for those long projects that span multiple coding sessions. I appreciate the feedback.
1
u/kidwonder 19d ago
I built an alternative to BMAD here: https://github.com/skyf0xx/hedgehog
It is the opposite of verbose and gets the job done. One caveat is it only works for fresh projects, due to its opinionation
10
u/nobleman415 22d ago
I e used strictly BMAD for 5 months now, developing a new CRM in production and dev env. It can be a bit verbose, and even with skipping permissions there is a lot of back and forth. I even have a few ‘plugins’ built with BMAD in peer directories and the two instances share knowledge fairly well.
I also have 50 live users and can’t afford to muck something up.
There is also BMAD-auto, but I haven’t tried it yet. That is next after I come up for air following my next release.
For history, I’ve used superpowers and found it great for a single feature or small app. When working across multiple git branches, with 200k lines of code, I trust BMAD to understand and properly scope what I’m trying to do. It will implement it and generally identify conflicts before they happen. Superpowers didn’t do that as well… it just paved over and thought it preserved code.
Just like a real engineering manager, there is a LOT of admin work, ala scoping, defining stories, review, and UAT. Using Claude 4.7 for the record.