The problem with vibe coding
Vibe coding is magical: you toss an idea at the AI, and it spits out code. Except after 30 minutes, the AI has forgotten what you told it at the start. It hallucinates features you never asked for, ignores half your codebase.
What if you could have the magic of vibe coding combined with the rigor of an engineering team?
The BMAD team
BMAD simulates a complete team:
- Architect - thinks through your system
- Product Owner - structures your specs
- Scrum Master - breaks things down into tasks
- Developer - codes cleanly without hallucinating
- Brainstormer - knows the 11 best brainstorming techniques
The Analyst agent and brainstorming
The Analyst agent (Mary) launches an interactive brainstorming session. You give it a vague idea, and it walks you through 3 brainstorming techniques out of the 11 it knows:
- What-if scenarios - provocative questions
- Analogical thinking - analogies from other fields
- Reversal/inversion - "How would you make this useless?"
- First principles - breaking things down to fundamentals
- Role-playing - stepping into the personas' shoes
Example: role-playing with 3 personas
The agent creates 3 characters and asks questions from each one's point of view:
- The curious junior dev - brain exhausted after work, wants easy content
- The senior lead - hates bullshit, looks for real breakthroughs
- The curious non-dev - interested in success stories and simplifications
This process surfaces criteria you wouldn't have identified on your own.
The 11 brainstorming techniques
Brainstorming is a theorized art. The Analyst agent knows 11 techniques and picks the ones best suited to your idea. The result: a brainstorming.md file containing everything that was explored.
The PM and the PRD
The Product Manager takes the brainstorming and generates the PRD (Product Requirement Document) with:
- Required features
- Epics (large blocks)
- Stories (detailed tasks)
Stories are organized into separate files so as not to overload the context.
The Architect
The Architect takes the PRD and produces:
- Technical architecture with diagrams
- Execution pipeline with estimated times
- Project structure
Nothing is left to chance for the following steps.
The Developer
The Developer implements story by story. Each story has:
- A precise technical description
- Acceptance criteria
- A space for dev notes
When it loads a story, it will cherry-pick the architecture chapters it needs - no context overload.
Result: a project that works "first try"
The code is:
- Perfectly typed
- Tested (111+ tests in the example)
- Hallucination-free
- Maintainable
Development happened "coffee in one hand, phone in the other". The project could have been done without BMAD, but it would have been messier, less maintainable, and without the in-depth thinking that comes from brainstorming.
What BMAD teaches you
Beyond the tool itself, BMAD helps you understand:
- How agile development works in a company
- The inputs/outputs of each role
- The responsibilities of PM, Architect, Scrum Master, Dev
This is top-tier engineering culture, applicable in job interviews.