BMAD Quick Reference Guide

💡 Core guide to get started with BMAD in 5 minutes

1-Minute Summary#

# New feature development
/bmad  " feature description " 

 # Or apply BMAD to existing workflow
/dev:run --bmad  " feature description "

BMAD validates code quality through 4 phases reviewed by 7 specialists:

Analysis → Planning → Solutioning → Implementation
(Analyst)   (PM)      (Architect+UX)  (Developer)

Command Cheat Sheet#

Main Commands#

Commonly Used Options#

Key Checklist by Phase#

Phase 1: Analysis#

Responsible: Analyst

Pass criteria:

• Are requirements clear and measurable?
• Are AC written in BDD Gherkin format? ⭐
• Is there at least 1 @happy-path scenario?
• Is there at least 1 @error-handling scenario?

AC example (required format):

Feature: Author list screen

  @happy-path
  Scenario: View author list
    Given I am logged in as an admin
    When I navigate to the author list screen
    Then the author list is displayed

  @error-handling
  Scenario: List loading failure
    Given the server connection is unstable
    When I navigate to the author list screen
    Then an error message is displayed
    And a retry button is displayed

Phase 2: Planning#

Responsible: Product Manager

Pass criteria:

• Has an issue been created?
• Are Story Points between 1-8?
• Are appropriate labels assigned?
• Are dependencies specified?

Phase 3: Solutioning#

Responsible: Architect + UX Designer (parallel)

Architect checklist:

• Clean Architecture compliance (BLoC → UseCase → Repository)
• Dependency wiring appropriate (Pure DI, BlocProvider direct creation)
• API design review (when needed)

UX Designer checklist:

• CoUI component usage
• Layout appropriateness
• Accessibility consideration

Phase 4: Implementation#

Responsible: Flutter/Backend Developer, Scrum Master

Pass criteria:

• Branch name rule: feature/{issue_number}-{slug}
• melos run analyze pass
• Tests pass
• Code review complete

Gate Failure Response#

Check Failure Message#

# Check status
/bmad:status

# Specific phase details
/bmad:status --phase solutioning

Re-review Request#

# Re-review after applying feedback
/bmad:review --persona architect --retry

# Or re-verify gate
/bmad:gate --phase solutioning --retry

Common Failure Causes#

Emergency Mode#

Use only in emergencies such as production outages:

/bmad --emergency  " emergency fix description "

Constraints:

• Admin approval required
• Implementation gate still mandatory (lint, tests)
• Post-review required within 48 hours

Configuration File Location#

Disable Persona#

// .claude/config/bmad.json
{
   " personas " : {
     " ux-designer " : {  " enabled " : false }
  }
}

Related Documents#