██████╗ ███╗ ███╗ █████╗ ██████╗ ██╔══██╗████╗ ████║██╔══██╗██╔══██╗ ██████╔╝██╔████╔██║███████║██║ ██║ ██╔══██╗██║╚██╔╝██║██╔══██║██║ ██║ ██████╔╝██║ ╚═╝ ██║██║ ██║██████╔╝ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝
Learn BMAD
12 modules · pick any order · runs in Claude Code · bring your own build
Stop winging it. There's a method for this.
You know the loop: throw a prompt at the AI, get something back, realize it built the wrong thing, start over. It's not the AI's fault. There was no plan.
BMAD (Build More, Architect Dreams) is a framework that fixes that. It plans first, uses specialist agents instead of one AI wearing every hat, and keeps you in control at the decisions that matter. This course teaches you the why and the shape of it. Not the install steps. The actual thinking.
Here's the twist: the whole course runs on the one thing you actually want to build. You bring it at setup, and every module applies its BMAD idea to your project, not a toy example. The capstone turns it all into a one-page plan you can use.
Is this for you?
If you're learning to build things (apps, tools, side projects) and you've been mostly "vibing" at an AI and hoping it gets it right, yes. This is for you. It's beginner-first by design: no agile background, no engineering degree, no experience with the BMAD tooling required.
By the end, you'll be able to:
- Clearly explain to yourself why BMAD beats asking one AI for everything at once
- Name the four phases of the BMAD workflow and know what each one is for
- Decide, on purpose, how much process a given job actually needs
- Walk away with a real one-page BMAD plan for the project you brought to class
The big ideas
Four concepts that change how you build with AI. Each one has its own module (or two).
Why it matters
The five beliefs behind BMAD, and the specific ways "just ask the AI" breaks down on real projects.
The four phases
Analysis → Planning → Solutioning → Implementation. What each phase produces, and when to skip one.
Your AI crew
Specialist agents (analyst, PM, architect, dev) and when to put the whole team in one room (Party Mode).
Right-sizing it
Knowing when not to use the full method is as important as knowing when to. Quick-dev vs the whole workflow.
The 12 modules
A buffet, not a staircase. Pick whatever you're curious about. Each module stands on its own and opens with a "you don't need anything before this" primer. There's a recommended order if you want one (just ask the instructor), but you're free to wander.
Modules 10-12 are bonus/advanced. Great once you're comfortable with the basics, but never required.
What you need
This course runs inside Claude Code. Start, stop, and resume anytime.
- Claude Code installed and running
- A build idea; the instructor helps you sharpen it at setup
- Sonnet model works great. No need for Opus.
How to start
Three steps. The whole thing fits in a folder.
cd learn-bmad && claude in the terminalA note on this
This course was built because the BMAD Method has genuinely useful ideas, but its docs are dense and its install flow is deep. The ideas deserve a lighter, more human on-ramp. So: 12 short modules, no setup required, your own project as the running example, and Claude Code as the instructor.
The content is distilled faithfully from the official BMAD documentation. It's an independent learning aid, not affiliated with BMAD, and whenever the instructor isn't sure about something, it points you to the real docs instead of guessing.
Questions, corrections, or ideas? Open an issue on GitHub.