bmad

Execute BMAD framework-based workflow

항목	내용
Invoke	/bmad
Category	workflow
Complexity	high
MCP Servers	zenhub

/bmad#

Executes workflows reviewed by 7 personas using the BMAD (Breakthrough Method for Agile AI-Driven Development) framework.

Required Execution Protocol#

Important: BMAD workflows must pass mandatory gates across 4 phases.

Phase Execution Order#

Phase 1: ANALYSIS     → Analyst review
Phase 2: PLANNING     → PM review
Phase 3: SOLUTIONING  → Architect + UX Designer review (parallel)
Phase 4: IMPLEMENTATION → Flutter/Backend Dev + Scrum Master

Execution by Phase#

Phase 1: Analysis

// 💡 Conceptual pseudocode (Claude actually performs review as the Analyst persona)
const analysisResult = await analyzeRequirements({
  input: workContent,
  checks: [ " requirementClarity " ,  " scopeAppropriateness " ,  " acTestability " ],
});

if (!analysisResult.pass) {
  // Provide feedback and request revision
  return requestRevision(analysisResult.feedback);
}

Phase 2: Planning

// 💡 Actual MCP tool call example (Claude executes as the PM persona)
// Dynamic workspace info lookup
const workspace = await mcp__zenhub__getWorkspacePipelinesAndRepositories();
const repoId = workspace.repositories.find(r = >   /* GitHub repo selection */).id;
const issueTypes = await mcp__zenhub__getIssueTypes();
const backlog = workspace.pipelines.find(p = >   p.name ===  " Product Backlog " );

const issue = await mcp__zenhub__createGitHubIssue({
  repositoryId: repoId,
  title: `${type}(${scope}): ${gitmoji} ${description}`,
  body: generateIssueBody(analysisResult),
  issueTypeId: issueTypes.find(t = >   t.name === type).id,
  labels: [type, scope],
});

await mcp__zenhub__setIssueEstimate({
  issueId: issue.id,
  estimate: storyPoint,
});

await mcp__zenhub__moveIssueToPipeline({
  issueId: issue.graphqlId,
  pipelineId: backlog.id,
});

Phase 3: Solutioning (parallel)

// 💡 Conceptual pseudocode (Claude actually calls Task tool in parallel)
const [architectResult, uxResult] = await Promise.all([
  Task({
    subagent_type:  " architect-review " ,
    prompt: `Architecture review: ${issue.title}`,
  }),
  Task({
    subagent_type:  " ux-designer-review " ,
    prompt: `UX review: ${issue.title}`,
  }),
]);

// All reviews must pass
if (!architectResult.pass || !uxResult.pass) {
  return requestRevision(combineFeedback(architectResult, uxResult));
}

Phase 4: Implementation

# Execute existing workflow Steps 4-12
# Create branch
git checkout development  & &   git pull origin development
git checkout -b feature/issue-${issue.number}-${slug}

# Move to In Progress
mcp__zenhub__moveIssueToPipeline(...)

# Implement, test, lint, PR, review, merge
# (same flow as the existing workflow)

Triggers#

When starting a new feature/bug/refactoring task
For complex tasks requiring persona-based review
For critical tasks requiring quality gates

Usage#

Basic Usage#

# Start BMAD workflow
/bmad  " Add author list screen "

Integration with Existing Workflow#

# Activate with --bmad option
/dev:run --bmad  " Add author list screen "

Activate Specific Gates Only#

# Analysis and Planning gates only
/bmad --gates analysis,planning  " Simple task "

Emergency Mode#

# Streamlined gates (requires user approval)
/bmad --emergency  " Production emergency fix "

Emergency Mode Approval Procedure:

// Claude requests explicit approval via AskUserQuestion tool
AskUserQuestion({
  questions: [{
    header:  " Emergency " ,
    question:  " Do you want to activate emergency mode? This will streamline the Analysis/Planning gates. " ,
    options: [
      { label:  " Yes, approved " , description:  " Activate emergency mode (post-review required within 48 hours) "   },
      { label:  " No " , description:  " Proceed in normal mode "   }
    ],
    multiSelect: false
  }]
});

Approval Request: Claude requests explicit approval via AskUserQuestion tool
User Selection: Proceed only when "Yes, approved" is selected
Gate Streamlining: Analysis, Planning gates are streamlined (not fully skipped)
Mandatory Gates: Implementation gate is always mandatory (lint, tests)
Post-Review: Post-review is required within 48 hours of completion (see BMAD_020 error code)

Parameters#

Parameter	Required	Description	Example
`task description`	✅	Description of the task	`"Add author list screen"`

Options#

Option	Default	Description
`--gates`	All gates	Activate specific gates only
`--emergency`	false	Emergency mode (streamlined gates)
`--no-parallel`	false	Disable parallel execution
`--skip-persona`	-	Skip specific persona

Output Format#

Progress#

╔════════════════════════════════════════════════════════════════╗
║  BMAD Workflow:  " Add author list screen "                             ║
╠════════════════════════════════════════════════════════════════╣
║                                                                ║
║  Phase 1: ANALYSIS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅         ║
║  ├── 🔍 Analyst review                                           ║
║  │   ├── ✅ Requirements clarity                                     ║
║  │   ├── ✅ Scope appropriateness                                       ║
║  │   └── ✅ Acceptance Criteria testability                    ║
║  └── 📋 Result: Approved (3 Acceptance Criteria confirmed)               ║
║                                                                ║
║  Phase 2: PLANNING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅          ║
║  ├── 📝 PM review                                                ║
║  │   ├── ✅ Epic/Story structure                                    ║
║  │   ├── ✅ Story Point: 5                                     ║
║  │   └── ✅ Dependencies: None                                       ║
║  └── 📋 Result: Issue #1810 created                                 ║
║                                                                ║
║  Phase 3: SOLUTIONING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🔄         ║
║  ├── 🏗️ Architect review (parallel)                                  ║
║  │   └── 🔄 Reviewing...                                         ║
║  └── 🎨 UX Designer review (parallel)                                ║
║      └── ✅ Complete                                                ║
║                                                                ║
║  Phase 4: IMPLEMENTATION ━━━━━━━━━━━━━━━━━━━━━━━━━━ ⏳         ║
║  └── Waiting                                                   ║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

Gate Failure (with error code)#

╔════════════════════════════════════════════════════════════════╗
║  BMAD Gate Failed: BMAD_003                                    ║
╠════════════════════════════════════════════════════════════════╣
║                                                                ║
║  Phase 3: SOLUTIONING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ❌         ║
║  ├── 🏗️ Architect review: ❌ FAILED                            ║
║  │   ├── ❌ DI structure: BLoC directly accesses Repository    ║
║  │   ├── 📋 Required action: Create UseCase, change dependency ║
║  │   └── 🔄 Retry: 1/3                                        ║
║  └── 🎨 UX Designer review: ✅ PASSED                          ║
║                                                                ║
║  💡 Fix: Apply feedback, then `/bmad:review --persona architect`║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

Completion#

╔════════════════════════════════════════════════════════════════╗
║  BMAD Workflow Complete:  " Add author list screen "                    ║
╠════════════════════════════════════════════════════════════════╣
║                                                                ║
║  📋 Issue: #1810 - Add author list screen                         ║
║  🔀 PR: #1815                                                  ║
║  🌿 Branch: feature/1810-author-list (deleted)                 ║
║                                                                ║
║  ✅ Persona review: 7/7 passed                                     ║
║  ✅ Gates passed: 4/4 phases                                     ║
║  ✅ Tests: 25/25 passed                                         ║
║                                                                ║
║  🏁 Final State: CLOSED                                        ║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

Self-Verification Checklist#

Phase	Gate	Done
Analysis	Requirements clarity	⬜
Analysis	Scope appropriateness	⬜
Analysis	Acceptance Criteria testability	⬜
Planning	Epic/Story structure	⬜
Planning	Story Point (1-8)	⬜
Planning	Labeling	⬜
Planning	Dependencies	⬜
Solutioning	Clean Architecture	⬜
Solutioning	DI structure	⬜
Solutioning	CoUI compliance	⬜
Implementation	Branch rules	⬜
Implementation	Lint pass	⬜
Implementation	Test pass	⬜
Implementation	Code review	⬜

/bmad:review - Persona-specific review
/bmad:status - Status check
/bmad:gate - Gate verification
/dev:run - Existing workflow (without BMAD)
/dev:run --bmad - BMAD integrated workflow

.claude/orchestrators/bmad-orchestrator.md - Orchestrator
.claude/orchestrators/phase-gates.md - Gate definitions
.claude/personas/ - Persona definitions
.claude/skills/bmad/SKILL.md - Skill details

bmad

/bmad#

Required Execution Protocol#

Phase Execution Order#

Execution by Phase#

Phase 1: Analysis

Phase 2: Planning

Phase 3: Solutioning (parallel)

Phase 4: Implementation

Triggers#

Usage#

Basic Usage#

Integration with Existing Workflow#

Activate Specific Gates Only#

Emergency Mode#

Parameters#

Options#

Output Format#

Progress#

Gate Failure (with error code)#

Completion#

Self-Verification Checklist#

Related Commands#

Related Documents#