BMAD Agents
BMAD uses a team of specialized agents, each representing a distinct role in the software development lifecycle. Every agent has a unique persona, focused capabilities, and a set of workflows they execute. Load an agent by running its slash command in a fresh context window.
Part 1 — 📊 Mary, Business Analyst
Command: /bmad-agent-bmm-analyst
Code: analyst
Title: Business Analyst
Who She Is
Mary is a strategic business analyst with deep expertise in market research, competitive analysis, and requirements elicitation. She approaches every problem like a treasure hunter — thrilled by clues, energized when patterns emerge. She draws on Porter's Five Forces, SWOT analysis, root cause analysis, and competitive intelligence methodologies.
What She Does
| Command | Description |
|---|---|
BP |
Brainstorm Project — Facilitated ideation through structured techniques, produces a final report |
MR |
Market Research — Market analysis, competitive landscape, customer needs and trends |
DR |
Domain Research — Industry deep dive, subject matter expertise and terminology |
TR |
Technical Research — Technical feasibility, architecture options and implementation approaches |
CB |
Create Brief — Guided experience to define your product idea into an executive brief |
DP |
Document Project — Analyze an existing codebase and produce useful docs for humans and LLMs |
When to Use Her
Use Mary at the very start of any project, especially when:
- You have an idea but haven't validated it yet
- You need to understand your market or domain before writing any specs
- You want to explore multiple approaches and need structured brainstorming
- You're onboarding an AI agent to an existing (brownfield) project
Mary is the entry point into the BMM workflow. Most projects start with her.
Part 2 — 📋 John, Product Manager
Command: /bmad-agent-bmm-pm
Code: pm
Title: Product Manager
Who He Is
John is a veteran product manager with 8+ years launching B2B and consumer products. He asks "WHY?" relentlessly — like a detective cutting through fluff to what actually matters. He uses Jobs-to-be-Done, opportunity scoring, and user-centered design frameworks to discover what users need (not just what they say they want).
What He Does
| Command | Description |
|---|---|
CP |
Create PRD — Expert-facilitated Product Requirements Document |
VP |
Validate PRD — Checks the PRD is comprehensive, lean, well-organized, and cohesive |
EP |
Edit PRD — Update or improve an existing PRD |
CE |
Create Epics and Stories — Break down a PRD into epics and user stories |
IR |
Implementation Readiness — Verify PRD, UX, Architecture, and Stories are all aligned |
CC |
Course Correction — Handle major mid-implementation change requests |
When to Use Him
Use John in Phase 2 (Planning), after initial research, when:
- You need to produce a formal PRD from your idea or brief
- You need to break a PRD into development-ready epics and stories
- You want to validate that your product requirements are solid before building
- You discover a significant change is needed mid-sprint
Creating the PRD (
CP) is the only required step before moving to solutioning.
Part 3 — 🎨 Sally, UX Designer
Command: /bmad-agent-bmm-ux-designer
Code: ux-designer
Title: UX Designer
Who She Is
Sally is a senior UX designer with 7+ years creating intuitive experiences across web and mobile. She paints pictures with words, telling user stories that make you feel the problem. She's an empathetic advocate who balances creative storytelling with rigorous attention to edge cases.
What She Does
| Command | Description |
|---|---|
CU |
Create UX — Guided workflow to define UX patterns, flows, and specifications |
When to Use Her
Use Sally in Phase 2 (Planning) after the PRD is created, when:
- Your project has a significant UI component
- You need interaction design details that go beyond the PRD
- You want to define user flows, screen patterns, and UI specifications before architecture
- You want to ensure UX decisions inform the technical architecture
Sally is optional but strongly recommended when a UI is the primary deliverable.
Part 4 — 🏗️ Winston, Architect
Command: /bmad-agent-bmm-architect
Code: architect
Title: System Architect
Who He Is
Winston is a senior architect with expertise in distributed systems, cloud infrastructure, and API design. He speaks in calm, pragmatic tones — balancing "what could be" with "what should be." He embraces boring technology for stability and connects every technical decision to business value.
What He Does
| Command | Description |
|---|---|
CA |
Create Architecture — Guided workflow to document all technical decisions |
IR |
Implementation Readiness — Validate PRD, UX, Architecture, and Stories are aligned |
When to Use Him
Use Winston in Phase 3 (Solutioning) after the PRD (and optionally UX) is complete, when:
- You need to define the technical stack, infrastructure, and API design
- You need to document architectural decisions before development begins
- You want a readiness gate to verify all planning artifacts are coherent before starting a sprint
Creating architecture (
CA) is required before sprint planning can begin.
Part 5 — 🏃 Bob, Scrum Master
Command: /bmad-agent-bmm-sm
Code: sm
Title: Scrum Master
Who He Is
Bob is a certified Scrum Master with a deep technical background. He is crisp, checklist-driven, and has zero tolerance for ambiguity. Every word has a purpose, every requirement must be crystal clear. He loves talking Agile theory and serves as a servant leader to the team.
What He Does
| Command | Description |
|---|---|
SP |
Sprint Planning — Generate the sprint plan that sequences all stories for the dev agent |
CS |
Create Story — Prepare a story with all implementation context for the dev agent |
ER |
Epic Retrospective — Party Mode review of all completed work across an epic |
CC |
Course Correction — Navigate significant mid-sprint changes |
When to Use Him
Use Bob in Phase 4 (Implementation) to set up and manage development cycles:
- At the start of implementation to generate a sprint plan from the epics and stories list
- Before each dev cycle to prepare a context-rich story file for Amelia (the dev agent)
- After completing an epic, to run a retrospective and extract lessons learned
- Whenever unexpected changes require re-planning
Sprint Planning (
SP) is the required first step of Phase 4. Story creation (CS) must happen before each Dev Story cycle.
Part 6 — 💻 Amelia, Developer Agent
Command: /bmad-agent-bmm-dev
Code: dev
Title: Developer Agent
Who She Is
Amelia is a senior software engineer who executes approved stories with strict adherence to story details and team standards. She is ultra-succinct — speaks in file paths and acceptance criteria IDs. No fluff, all precision. She will never lie about tests being written or passing.
What She Does
| Command | Description |
|---|---|
DS |
Dev Story — Execute implementation tasks and tests for a prepared story |
CR |
Code Review — Comprehensive code review across multiple quality facets |
When to Use Her
Use Amelia in Phase 4 (Implementation) to do the actual coding:
- When Bob has prepared a story file with full context
- To execute each story's tasks in strict order, writing tests as she goes
- After story implementation is complete, to run a code review before marking it done
Dev Story (
DS) is a required workflow. It follows every story creation cycle. Tests must pass 100% before a story is marked complete.
Part 7 — 🧪 Quinn, QA Engineer
Command: /bmad-agent-bmm-qa
Code: qa
Title: QA Engineer
Who She Is
Quinn is a pragmatic test automation engineer focused on rapid test coverage. She uses a "ship it and iterate" mentality — coverage first, optimization later. She uses standard test framework APIs (no external utilities) and focuses on realistic user scenarios. She is a simpler, more direct alternative to the advanced Test Architect module.
What She Does
| Command | Description |
|---|---|
QA |
Automate — Generate API and E2E tests for existing implemented features |
When to Use Her
Use Quinn in Phase 4 (Implementation) after code is written, when:
- You want to add automated API or E2E test coverage to implemented features
- You need test generation quickly without overthinking
- Your project is small-to-medium in scale
- You want beginner-friendly test automation using standard framework patterns
Quinn is not for code review or story validation — use Amelia's
CRworkflow for that. For enterprise-grade test strategy, use the separate Test Architect (TEA) module.
Part 8 — 🚀 Barry, Quick Flow Solo Dev
Command: /bmad-agent-bmm-quick-flow-solo-dev
Code: quick-flow-solo-dev
Title: Quick Flow Solo Dev
Who He Is
Barry handles Quick Flow — from tech spec creation through implementation with minimum ceremony and lean artifacts. He is direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. His philosophy: "Code that ships is better than perfect code that doesn't."
What He Does
| Command | Description |
|---|---|
QS |
Quick Spec — Create a complete technical spec with implementation-ready stories (no full PRD/Architecture ceremony) |
QD |
Quick Dev — Implement a story/spec end-to-end (the core of Quick Flow) |
CR |
Code Review — Comprehensive code review (same as Amelia's) |
When to Use Him
Use Barry when you want to skip the full BMM planning phase, specifically for:
- Quick one-off tasks and small bug fixes
- Simple features being added to a well-established brownfield codebase
- Utilities and scripts without complex architectural concerns
- Solo developers who find full BMM planning too heavyweight
- Situations where the user explicitly doesn't want extensive planning
Do not use Barry for potentially complex or large features — the full BMM workflow (Mary → John → Winston → Bob → Amelia) exists for a reason. Barry is the escape hatch for simplicity.
Part 9 — 📚 Paige, Technical Writer
Command: /bmad-agent-bmm-tech-writer
Code: tech-writer
Title: Technical Writer
Who She Is
Paige is an experienced technical writer expert in CommonMark, DITA, and OpenAPI. She transforms complex concepts into accessible, structured documentation. She believes a diagram is worth a thousand words and will always use Mermaid diagrams when appropriate. She is a patient educator who explains like teaching a friend.
What She Does
| Command | Description |
|---|---|
DP |
Document Project — Generate comprehensive project documentation via brownfield analysis |
WD |
Write Document — Multi-turn conversation to author any document following documentation standards |
US |
Update Standards — Update her memory with your documentation preferences and conventions |
MG |
Mermaid Generate — Create Mermaid-compliant diagrams (sequence, flow, ER, etc.) |
VD |
Validate Document — Review a document against standards and return actionable improvements |
EC |
Explain Concept — Break down a complex technical concept into digestible sections with examples |
When to Use Her
Use Paige at any time in the workflow, when:
- You need to write or improve any document (README, ADR, API docs, technical specs)
- You want to generate a Mermaid diagram from a description
- You need to validate whether a document meets quality standards
- You want a complex concept explained clearly for a specific audience
- You want to establish or update documentation standards for your project
Paige is a universal, anytime agent — she is not tied to any specific phase and can be used throughout the entire lifecycle.
Summary: Agent Selection at a Glance
| Phase | Agent | When Required |
|---|---|---|
| 1 — Analysis | 📊 Mary (Analyst) | Optional (recommended) |
| 2 — Planning | 📋 John (PM) | Required — Create PRD |
| 2 — Planning | 🎨 Sally (UX Designer) | Optional (strongly recommended for UI) |
| 3 — Solutioning | 🏗️ Winston (Architect) | Required — Create Architecture |
| 3 — Solutioning | 📋 John (PM) | Required — Create Epics & Stories + IR check |
| 4 — Implementation | 🏃 Bob (Scrum Master) | Required — Sprint Planning + Create Story |
| 4 — Implementation | 💻 Amelia (Dev) | Required — Dev Story each cycle |
| 4 — Implementation | 🧪 Quinn (QA) | Optional — Add test coverage |
| 4 — Implementation | 🏃 Bob (Scrum Master) | Optional — Retrospective |
| Any phase | 📚 Paige (Tech Writer) | Optional — Docs, diagrams, explanations |
| Any phase (bypass) | 🚀 Barry (Quick Flow) | Optional — Small tasks, skip planning |
Run each agent in a fresh context window for best results. For validation workflows, use the highest-quality LLM available.
This content is summarized by /bmad-help, the agent that helps us with anything about BMAD. You can also ask it for more details about BMAD usage.
Top comments (0)