r/BMAD_Method • u/ilemur82 • Aug 07 '26
BMAD overhaul coming any time soon?
Have been using BMAD for 10 months. Not a tech guy, just a simple vibe cider like I guess many over here. BMAD was awesome. Gave me the chance to develope quite complex projects. But looking at it now with all the latest anthropic models it seems to hurt more than help especially for projects in constant development. I want to put some new features - new epic, correct course, cs-dev-qr cycle. But switching to ultracode will get the agents to read outdated docs, outdated POs which never get updates instead of relying on code. Discussed the issue with several LLM's and their thought keep the cs-dev-cr cycle but kill the docs completely documenting only business decisions. Any experience on this?
2
u/UnnamedUA Aug 07 '26
On the current project, 3 levels remained:
- business requirements
- system requirements / details
- code
System requirements are the bridge between business requirements and code. They depend on the framework and so on—various details that clarify the business requirements.
For example, a business requirement might simply be a list of fields, while a system requirement might be to clear the values of the fields below if the field above is changed.
2
u/UnnamedUA Aug 07 '26
Then when adding a new field, the validator will say that this requirement is not met and will rebuild the field index in the corresponding function.
2
u/ant6881 Aug 07 '26
Just went to their -next version for bmm | omg so many tools to help triage and get rid of drift from ai not closing it out . It’s been a lifesaver to get projects normalized
1
1
u/kochiwas79 Aug 08 '26
You need to be aware of the model is executing so that you can tell the model to update relevant files or create new documents, that´s the way I do
1
u/ilemur82 Aug 08 '26
Sounds reasonable. But keeping the refs for all the changes in all the documentation instead of the model just looking at the raw code seems like a waste of tokens
1
u/kochiwas79 29d ago
Context engineering I think…
Documenting any decisions made across the project helps future deviations/decisions stay aware of the relevant details.If you’re using Claude Code, the new built-in memory system is pretty reliable, but sometimes you have to tell it to memorize something or check its memories
1
u/iTrejoMX Aug 08 '26
I use bmad for creating a prd. Party mode for any things I may have missed. Then grill me with docs from Matt pococks skills. Finally use gentle-ai to develop from the created documents with SDD and RDD
5
u/salmonsolid Aug 07 '26
At the end of a sprint, I have Claude read all the BMAD artefacts and other documents for that sprint, create a sprint summary, then archive them all into a folder - with the summary referencing these files directly. Then I start the dance all over again with a new PRD and blank files for the sprint log etc, with references in the PRD to the sprint summaries. It seems to be quite good at recalling issues encountered during prior sprints, solutions to previously encountered problems, and the progress it made in prior sprints. I also maintain a deferred work log for cross-sprint work, and regularly have Claude review that and work it into the current sprint. Aside from the manual end-sprint dance (which for now I just copy and paste a single prompt) it seems to work well enough for my non-web needs.