How To - What I Should Have Done First: BMAD Workflow Lessons from a YOLO Vibe Coder
Source: Our analysis of the creator's lived experience, based on what they said in this video.
Creator's Key Takeaways
I've been pretty much doing it uh yolo, you only live once.
It is never, and I mean never, a straightthrough, oneshot, highly successful thing.
We talk past each other. We talk at each other. We do do not often talk with each other.
I am showing you real world team behavior in the context of working with artificial intelligence.
Creator's Tips & Advice
🆕New to Cruising? This Creator Addresses:
Questions This Creator Answers
YouTube Video Description↓
In this episode of Tim Unscripted, I hit pause on YOLO vibe-coding and finally walk through what I should have done before ever firing up the BMAD agents. Why this video exists A candid retrospective on jumping straight into BMAD without really following the workflow guide or recommended sequence of agents. How that “just make it work” mindset mirrors real product teams and leads to rework, confusion, and missed expectations with both humans and AI. An invitation to use my mistakes as a shortcut so you can adopt BMAD more deliberately instead of learning everything the hard way. Getting grounded in the BMAD method A tour of BMAD’s public website and GitHub repo, including the scripts that bootstrap all the method files into your IDE. The difference between “just pull some files down” and using the installer scripts that set up agents, workflows, and rules correctly from the start. Why running BMAD through an IDE (VS Code, Cursor, Windsurf, etc.) makes life easier than trying to wire markdown and LLMs together by hand. The workflow I should have followed Stepping through the official BMAD workflow guide and calling out which steps are required vs optional. How a more disciplined path—analyst brainstorming and research, product brief, then PM-created PRD—would have reduced confusion later. Real talk on how my “skip the product brief, go straight to PRD” choice mirrors the way human teams regularly create avoidable rework. Human teams, AI agents, and miscommunication How talking at agents instead of with them echoes the same misalignment we see on real product teams. Why hybrid human–AI teams will amplify our existing collaboration issues unless we get intentional about process and communication. Using BMAD as a transparency tool to expose where understanding breaks down, both between people and between people and agents. A plea for QA and better practice DISCLAIMER -- This was recorded and edited BEFORE a conversation with one of my colleagues. I was corrected on the Test Engineering Architect persona and "fixed" my own problem. An argument for incorporating a dedicated QA/testing agent and workflow into BMAD to keep quality from becoming an afterthought. Perspective from my past life in QA and process engineering on why a second set of eyes still matters in an AI-heavy world. How this whole experience is giving me new stories and examples to bring back to the teams I coach and work with. If you want to see how an “AI conductor” with decades in product work can still bungle the process—and how BMAD helps make those mistakes visible—watch this episode and subscribe for more warts-and-all how-tos from Tim Unscripted.