Level 9Lesson 76⏱️ 45 min

BMAD Part 1 - Your AI Product Team

BMAD turns one AI into a whole product team - analyst, PM, architect, developer, QA - each a focused expert that checks the others' work

What BMAD Is

BMAD stands for Breakthrough Method for Agile AI-Driven Development. It's a free, open-source framework (around 49,000 GitHub stars by mid-2026, on version 6) with one big idea: instead of asking a single AI to do everything, you run a team of specialized AI agents that mirror a real software team - and they hold each other accountable.

The problem it solves: a single AI doing "everything" produces average, black-box code - fast output that hides the intent and decisions behind it. BMAD makes AI a disciplined participant in an agile process instead of a clever wildcard.

Why a "Team" Beats One Super-Agent

You learned in Level 7 that the maker shouldn't grade its own homework, and in Level 8 that each agent works best with a tight, focused context. BMAD applies both ideas at once: each agent has one role and a narrow context, so every AI call stays focused and high-quality, and each role checks the work of the previous one.

The compounding effect: because each agent adds and validates context as the work moves down the line, misunderstandings get caught early - when they're cheap to fix - instead of surfacing in finished code.

Meet the Team (12+ Agents)

BMAD ships specialized agents that mirror an agile team. The core cast:

PLANNING ROLES
  Analyst        explores the idea, surfaces constraints → writes the brief
  Product Manager turns the brief into a PRD (with FRs & NFRs)
  Architect      designs components, data flow, tech choices
  Product Owner  aligns the docs, runs checklists, shards big specs

BUILDING ROLES
  Scrum Master   splits epics into precise, context-rich story files
  Developer      implements one story at a time, with tests, on a branch
  QA             reviews, designs tests, refactors for quality

COORDINATION
  Orchestrator   routes each task to the right agent, enforces the order
They're just text files. Each agent is defined in plain Markdown/YAML describing its persona, its commands, and what it depends on. You can read them, edit them, and commit them to Git like any other code. No magic - just well-scoped roles.

The Big Rule: Documents Are the Source of Truth

This is BMAD's heartbeat and the through-line of this whole level. In BMAD, the source of truth is not the code - it's the documents: the brief, the PRD, the architecture, the stories. Code is generated from those, and every document is a living file versioned in Git.

Normal project:   code is truth  →  docs rot  →  nobody trusts the docs
BMAD project:     docs are truth →  code follows →  docs always current

Result: a new engineer reads the docs and actually understands the system,
because the docs are what the code was built from.

Two Phases (The Shape of It)

BMAD splits any project into two clean phases. We'll walk the full workflow next lesson; here's the map:

Phase 1 - Agentic Planning

The planning agents (Analyst, PM, Architect, Product Owner) produce and refine all the key documents before any code is written: brief → PRD → architecture → alignment checklist. Everything versioned in Git.

Phase 2 - Context-Engineered Development

The Scrum Master shards the plan into small, context-rich story files; the Developer builds each on its own branch with tests; QA and automated checks review before merge. Every story links back to the PRD and architecture.

Notice the name of phase 2. "Context-Engineered Development" is Level 8 by another name - each story file is a tight, high-signal context package for the Developer agent. BMAD is context engineering wrapped in an agile process.

A Few Nice Touches

Things BMAD adds on top:
  • Scale-adaptive: it adjusts planning depth automatically - a bug fix gets a light process, an enterprise system gets the full treatment.
  • Party mode: bring multiple agent personas into one session to discuss a decision together (like a design meeting).
  • Web bundles: do the heavy planning (brief, PRD, research) in a flat-rate ChatGPT or Gemini subscription, then bring the polished docs into your coding tool - a real cost saver on long projects.
  • bmad-help: an assistant that tells you what step comes next if you're lost.

Hands-On: Cast Your Team

Hands-on (10 min): Take a small app idea. For each BMAD role (Analyst, PM, Architect, Scrum Master, Developer, QA), write one sentence describing what that specific agent would produce for your idea. Example for a tip calculator - Analyst: "who uses it and the constraint that it must work offline"; PM: "the FRs and NFRs"; etc. This makes the team concrete and previews exactly what you'll generate in the worked example two lessons from now.
Lesson 76 Quick Reference
BMAD

Breakthrough Method for Agile AI-Driven Development - an open-source framework using a team of specialized AI agents

Why a team

Each agent has one role and a narrow context, stays focused, and checks the previous agent's work

The agents

Analyst, PM, Architect, Product Owner (plan) + Scrum Master, Developer, QA (build) + Orchestrator

Agents are text files

Each role is plain Markdown/YAML (persona, commands, dependencies) you can read, edit, and commit

Docs are the source of truth

Brief, PRD, architecture, stories drive the code; everything versioned in Git

Two phases

Agentic Planning (docs first) then Context-Engineered Development (sharded stories → code)

← The SDD Toolbox
Unlocks in ~12 min of reading