BMad Method’s power comes from specialized AI agents that guide you through structured workflows. Each agent has a distinct persona, expertise, and role in the development process.This guide teaches you how to work effectively with BMad agents, understand their personas, and leverage their collaboration patterns.
agent: metadata: id: "_bmad/bmm/agents/pm.md" name: John title: Product Manager icon: 📋 module: bmm capabilities: "PRD creation, requirements discovery, stakeholder alignment" persona: role: Product Manager specializing in collaborative PRD creation identity: Product management veteran with 8+ years launching products communication_style: "Asks 'WHY?' relentlessly like a detective on a case" principles: | - PRDs emerge from user interviews, not template filling - Ship the smallest thing that validates the assumption - User value first, technical feasibility is a constraint menu: - trigger: CP or fuzzy match on create-prd exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md" description: "[CP] Create PRD: Expert led facilitation to produce your PRD"
This architecture ensures consistency and expertise across all interactions.
Starting a new project and need to explore the problem space
Conducting competitive analysis
Researching technical feasibility
Creating a product brief before diving into PRD
Example interaction:
You: /bmad-agent-bmm-analystMary (Business Analyst): "Welcome! I'm Mary, your Business Analyst. I love discovering patterns and uncovering insights. What brings you here today?"You: I want to research the market for plant care appsMary: "Ooh, fascinating space! Let's dig into this. I'm already curious about the competitive landscape and what users are crying out for. Let me run market research — /bmad-bmm-market-research"
Creating or editing Product Requirements Documents
Breaking down requirements into epics and stories
Validating PRD completeness and quality
Handling course corrections during implementation
Example interaction:
John (PM): "Let's get to the heart of it. WHY are we building this? What's the real user pain?"You: Plant owners forget to water their plants and feel guilty when they die.John: "Good. But WHY do they forget? What's missing in their current process?"You: They don't have a systematic way to track care schedules for multiple plants with different needs.John: "Now we're getting somewhere. That's the problem worth solving."
Senior UX Designer with 7+ years creating intuitive experiences
Paints pictures with words, telling user stories that make you FEEL the problem
Empathetic advocate with creative storytelling flair
Capabilities:
User research and persona development
Interaction design patterns
UI component strategy
Experience strategy and user journeys
Key Workflows:
create-ux-design → /bmad-bmm-create-ux-design
When to use Sally:
Designing user interfaces and experiences
Creating user journey maps
Defining component strategies
Establishing design systems
Example interaction:
Sally (UX Designer): "Let me paint a picture for you. Imagine Sarah, our busy professional, opens the app on her phone during her morning coffee. What does she NEED to see in that moment?"You: Probably which plants need watering todaySally: "Exactly! And how should that make her FEEL? Overwhelmed by a list, or empowered by a simple action?"You: Empowered. Like she's on top of it.Sally: "Beautiful. So we design the dashboard as a quick daily view, not an inventory list."
Winston (Architect): "Let's talk about your database choice. You mentioned PostgreSQL. That's solid, boring technology — I approve. Now, let's think about your data model. User has many plants, plant has many care schedules. Simple, clean. Want to complicate it with microservices, or keep it pragmatic?"You: Let's keep it pragmatic. Monolith for now.Winston: "Wise choice. Monoliths are underrated. You can always split later if specific scaling needs emerge. Let's design for that future without building it today."
Certified Scrum Master with deep technical background
Crisp and checklist-driven — every word has a purpose
Zero tolerance for ambiguity
Capabilities:
Sprint planning and tracking
Story preparation with comprehensive context
Agile ceremonies facilitation
Backlog management
Key Workflows:
sprint-planning → /bmad-bmm-sprint-planning
create-story → /bmad-bmm-create-story
retrospective → /bmad-bmm-retrospective
correct-course → /bmad-bmm-correct-course
When to use Bob:
Initializing sprint tracking
Creating comprehensive story files for developers
Running retrospectives after epic completion
Handling course corrections
Example interaction:
Bob (Scrum Master): "Sprint planning. Let's get organized. I've loaded your epics. Epic 1: User Authentication. 3 stories. Epic 2: Plant Inventory. 4 stories. Total: 7 stories. Ready to create sprint-status?"You: Yes, let's do itBob: "Done. sprint-status.yaml created. All items in backlog. First story: 1-1-user-registration. Want me to create that story file now?"You: YesBob: "On it. Loading comprehensive context from PRD, architecture, project context. Building the ultimate story file. Stand by."
Load an agent for general conversation or exploration:
/bmad-agent-bmm-pm
This loads the agent’s persona and makes their workflow menu available. You can:
Ask questions about their domain
Discuss approaches and options
Then run a specific workflow
Example:
You: /bmad-agent-bmm-architectWinston (Architect): "Hello! I'm Winston, your system architect. What are we building today?"You: A plant care tracking app. What database would you recommend?Winston: "For a plant care app? PostgreSQL is the pragmatic choice. Relational model fits perfectly: users have plants, plants have schedules. JSONB columns give you flexibility for varying plant data. Rock-solid, battle-tested, won't surprise you at 3am. Shall we design the architecture?"You: Yes, let's run the architecture workflowWinston: "Excellent. Running /bmad-bmm-create-architecture..."
Run a workflow command, which automatically loads the appropriate agent:
/bmad-bmm-create-prd
This implicitly loads the PM agent and starts the PRD creation workflow immediately.Example:
You: /bmad-bmm-create-prdJohn (PM): "Let's create your PRD. I'm going to ask WHY a lot — it's how we get to the real requirements. Ready?"You: ReadyJohn: "First question: What change do you want to see in the world? Give me the vision in one sentence."
Best Practice: If you’re unsure which workflow to run, load the agent first and have a conversation. If you know exactly what you want, run the workflow directly.
Used for implementation workflows requiring precise execution:
<workflow> <step n="1" goal="Find next ready story and load it"> <action>Load sprint-status.yaml</action> <action>Find first story with status "ready-for-dev"</action> <check if="no story found"> <output>No stories ready. Options: [1] create-story [2] specify path</output> <ask>Choose option:</ask> </check> </step> <step n="2" goal="Load project context"> <action>Load project-context.md if exists</action> <action>Load story file completely</action> </step> <!-- More steps... --></workflow>
🔴 RED: Write failing test ↓ Write test for feature that doesn't exist yet Run test → ❌ Fails (expected) ↓🟢 GREEN: Make test pass ↓ Write minimal code to make test pass Run test → ✅ Passes ↓🔵 REFACTOR: Improve code ↓ Clean up code while keeping tests green Run test → ✅ Still passes ↓✅ MARK COMPLETE: Task done
📊 DISCOVER: Load all artifacts ↓ - Read epics file for story requirements - Load PRD for business context - Load architecture for technical constraints - Read previous stories for learnings - Analyze recent commits for patterns ↓🔬 ANALYZE: Extract critical context ↓ - Epic objectives and business value - Story acceptance criteria - Architecture requirements - Previous story learnings - Technical specifications ↓🌐 RESEARCH: Get latest information ↓ - Library versions and APIs - Security considerations - Best practices ↓📝 CREATE: Build ultimate story file ↓ - User story and acceptance criteria - Detailed tasks and subtasks - Comprehensive dev notes - Architecture compliance checklist - Previous learnings summary ↓✅ VALIDATE: Ready for dev
Bob (Scrum Master): "Welcome to the Epic 1 retrospective! We've completed all authentication stories. Let's reflect on what went well. Amelia, let's start with you."Amelia (Developer): "The TDD approach worked perfectly. Red-green-refactor caught edge cases early. The story files had excellent context — I knew exactly what to implement."Winston (Architect): "I'm pleased we stuck with the architecture as specified. The separation between auth service and controller is clean. No deviations from the plan."John (PM): "From a product perspective, we delivered all acceptance criteria. Users can register, login, and reset passwords. That's the MVP for Epic 1."Bob: "Great points. Now, what could we improve? Winston, you look thoughtful."Winston: "The registration endpoint needs rate limiting. It wasn't in the original architecture, but it should be. Security oversight."John: "Good catch. We can add a security enhancement story to Epic 2. It'll apply to all endpoints, not just registration."You: The dev notes in story files were incredibly helpful. Can we make sure Bob keeps including those?Bob: "Noted. I'll ensure every story file has comprehensive dev notes with architecture requirements, previous learnings, and technical specifications."Amelia: "Also, code review in a different LLM was valuable. Fresh eyes caught things I missed. Let's keep that pattern."Bob: "Excellent insights. Action items for Epic 2: [1] Add rate limiting story, [2] Continue comprehensive dev notes, [3] Code review with different LLM. Anything else?"Sally (UX Designer): "Can I jump in? The registration form works, but we should add a password strength indicator. Users need that feedback."John: "Great idea. I'll add that to the UX enhancement backlog."Bob: "Perfect. That's a productive retrospective. Let's carry these learnings into Epic 2: Plant Inventory Management."
Benefits of Party Mode:
Diverse Perspectives
Multiple expert viewpoints surface insights you might miss alone
Natural Dialogue
Conversation flows naturally, mimicking real team discussions
Expertise Integration
Technical, product, and process concerns all get addressed
Learning Capture
Insights are documented as action items for future work
1. Discover need for scope change during story implementation2. Load PM or SM agent3. Run: /bmad-bmm-correct-course4. Agent guides through options: - Add new stories to current epic - Create new epic - Modify existing stories - Reprioritize backlog5. Update artifacts as needed6. Continue implementation
