BMAD Orchestrator

BMAD framework main orchestrator

항목	내용
Version	1.0.0

Main orchestrator for the BMAD (Breakthrough Method for Agile AI-Driven Development) framework. 7 personas review and progress workflows through 4 phases.

Architecture Overview#

┌─────────────────────────────────────────────────────────────────┐
│                    BMAD Orchestrator                            │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ┌──────────────┐   ┌──────────────┐   ┌──────────────┐        │
│  │   Analysis   │ → │   Planning   │ → │ Solutioning  │ →      │
│  │    Phase     │   │    Phase     │   │    Phase     │        │
│  ├──────────────┤   ├──────────────┤   ├──────────────┤        │
│  │  🔍 Analyst  │   │  📝 PM       │   │  🏗️ Architect│        │
│  │              │   │              │   │  🎨 UX Desig.│        │
│  └──────┬───────┘   └──────┬───────┘   └──────┬───────┘        │
│         │                  │                  │                 │
│         ▼                  ▼                  ▼                 │
│  ┌──────────────────────────────────────────────────────┐      │
│  │              Implementation Phase                     │      │
│  ├──────────────────────────────────────────────────────┤      │
│  │  🧑‍💻 Flutter Dev  │  🔧 Backend Dev  │  📋 Scrum Master│      │
│  └──────────────────────────────────────────────────────┘      │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Phase Structure#

Phase 1: Analysis#

Item	Content
Responsible Persona	Analyst
Purpose	Requirements analysis, Acceptance Criteria definition, feasibility review
Input	Task description (text)
Output	Analyzed requirements, Acceptance Criteria list
Gate	Requirements clarity, scope appropriateness, Acceptance Criteria testability

Phase 2: Planning#

Item	Content
Responsible Persona	Product Manager
Purpose	Issue structuring, Story Point estimation, priority setting
Input	Phase 1 output
Output	Created issues, labels, dependencies
Gate	Epic/Story structure, Story Point, labeling, dependencies

Phase 3: Solutioning#

Item	Content
Responsible Persona	Architect + UX Designer (parallel)
Purpose	Architecture design, UI/UX review
Input	Phase 2 output
Output	Design document, UI guidelines
Gate	Clean Architecture, DI structure, CoUI compliance, accessibility

Phase 4: Implementation#

Item	Content
Responsible Persona	Flutter Dev + Backend Dev + Scrum Master
Purpose	Code implementation, testing, PR creation, merge
Input	Phase 3 output
Output	Completed code, tests, PR
Gate	Lint verification, test pass, code review

Execution Flow#

Full Flow#

                     ┌─────────────────────┐
                    │   Task Input           │
                    └──────────┬──────────┘
                               ▼
┌─────────────────────────────────────────────────────────────────┐
│ Phase 1: ANALYSIS                                               │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ Analyst review                                                 │ │
│ │ - Requirements clarity ✅                                         │ │
│ │ - Scope appropriateness ✅                                           │ │
│ │ - Acceptance Criteria testability ✅                        │ │
│ └─────────────────────────────────────────────────────────────┘ │
│                          GATE: PASS                             │
└─────────────────────────────┬───────────────────────────────────┘
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ Phase 2: PLANNING                                               │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ PM review                                                      │ │
│ │ - Epic/Story structure ✅                                         │ │
│ │ - Story Point ✅                                             │ │
│ │ - Labeling ✅                                                  │ │
│ │ - Dependencies ✅                                                  │ │
│ └─────────────────────────────────────────────────────────────┘ │
│                          GATE: PASS                             │
└─────────────────────────────┬───────────────────────────────────┘
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ Phase 3: SOLUTIONING (parallel execution)                                │
│ ┌─────────────────────────┐ ┌─────────────────────────┐        │
│ │ Architect review          │ │ UX Designer review        │        │
│ │ - Clean Architecture ✅ │ │ - CoUI compliance ✅          │        │
│ │ - DI structure ✅            │ │ - Layout ✅           │        │
│ │ - API design ✅           │ │ - Interaction ✅           │        │
│ └─────────────────────────┘ └─────────────────────────┘        │
│                          GATE: ALL PASS                         │
└─────────────────────────────┬───────────────────────────────────┘
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ Phase 4: IMPLEMENTATION                                         │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ Parallel work (if independent)                                    │ │
│ │ - Flutter Developer: UI implementation                                 │ │
│ │ - Backend Developer: API implementation                                │ │
│ │ - Scrum Master: Progress management                                    │ │
│ └─────────────────────────────────────────────────────────────┘ │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ Sequential work                                                    │ │
│ │ Step 4: Branch creation → Step 5: In Progress                   │ │
│ │ Step 6: BDD → Step 7: Implementation → Step 8: Tests                 │ │
│ │ Step 8.5: Lint verification → Step 9: PR creation                       │ │
│ │ Step 10: Review/QA → Step 11: Code review                     │ │
│ │ Step 12: Merge approval                                          │ │
│ └─────────────────────────────────────────────────────────────┘ │
│                          GATE: ALL PASS                         │
└─────────────────────────────┬───────────────────────────────────┘
                              ▼
                    ┌─────────────────────┐
                    │   Workflow Complete    │
                    └─────────────────────┘

Phase Gate Handling#

On Gate Success#

Phase {N} Gate: ✅ PASSED

Proceeding to the next phase.

On Gate Failure#

Phase {N} Gate: ❌ FAILED

Rejection reasons:
- {reason 1}
- {reason 2}

Required actions:
1. {action 1}
2. {action 2}

⚠️ Cannot proceed to the next phase.
   Re-review by the corresponding persona is required after completing the fixes.

Parallel Execution Patterns#

⚠️ 런타임 제공 페르소나 (이 플러그인이 배포하지 않음): 아래 fan-out 의 subagent_type(architect-review, ux-review, ux-designer-review, backend-developer, flutter-developer)는 호스트 프로젝트의 .claude/personas/ 가 공급하는 런타임 페르소나다(이 플러그인 agents/ 에 없음). dispatch 전 존재를 확인하고, 없으면 cc-product 의 실재 SKILL(architect, ux-designer, pm, developer)을 순차 호출하는 것으로 degrade하라(경고와 함께). 미존재 페르소나의 Task 결과를 PASS 로 간주하지 말 것.

Fan-out Pattern (Phase 3)#

// Architect and UX Designer parallel execution
const [architectResult, uxResult] = await Promise.all([
  Task({
    subagent_type:  " architect-review " ,
    prompt:  " Perform architecture review " ,
  }),
  Task({
    subagent_type:  " ux-review " ,
    prompt:  " Perform UX review " ,
  }),
]);

// All results must PASS to proceed to next step
if (architectResult.status ===  " PASSED "   & &   uxResult.status ===  " PASSED " ) {
  proceed();
} else {
  // Feedback loop for failed reviews
  handleFailedReviews([architectResult, uxResult]);
}

Independent Task Parallelization (Phase 4)#

// Parallel execution when Backend and Frontend are independent
if (isBackendIndependent(task)) {
  const [backendResult, frontendResult] = await Promise.all([
    Task({
      subagent_type:  " backend-developer " ,
      prompt:  " API implementation " ,
    }),
    Task({
      subagent_type:  " flutter-developer " ,
      prompt:  " Mock-based UI implementation " ,
    }),
  ]);
}

State Management#

Workflow State#

interface BMADState {
  currentPhase:  " analysis "   |  " planning "   |  " solutioning "   |  " implementation " ;
  phases: {
    analysis: PhaseState;
    planning: PhaseState;
    solutioning: PhaseState;
    implementation: PhaseState;
  };
  issue?: IssueInfo;
  branch?: string;
  pr?: PRInfo;
}

interface PhaseState {
  status:  " pending "   |  " in_progress "   |  " passed "   |  " failed " ;
  reviews: ReviewResult[];
  blockers: Blocker[];
}

State Transitions#

pending → in_progress → passed
                     ↘ failed → (fix) → in_progress

Command Interface#

Start Full Workflow#

# Start BMAD workflow
/product:bmad  " task description " 

 # Integrate with existing workflow
/dev:run --bmad  " task description "

Individual Persona Review#

# Execute specific persona review only
/product:review --persona analyst  " review target " 
 /product:review --persona architect  " current PR review "

Status Check#

# Check overall status
/product:bmad-status

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

Manual Gate Verification#

# Manual gate verification
/product:gate --phase analysis

Configuration#

settings.json Extension#

{
   " bmad " : {
     " enabled " : true,
     " strictGates " : true,
     " parallelExecution " : true,
     " phases " : {
       " analysis " : {  " required " : true },
       " planning " : {  " required " : true },
       " solutioning " : {  " required " : true },
       " implementation " : {  " required " : true }
    },
     " personas " : {
       " analyst " : {  " enabled " : true },
       " product-manager " : {  " enabled " : true },
       " architect " : {  " enabled " : true },
       " flutter-developer " : {  " enabled " : true },
       " backend-developer " : {  " enabled " : true },
       " scrum-master " : {  " enabled " : true },
       " ux-designer " : {  " enabled " : true }
    }
  }
}

Output Format#

Progress Display#

╔════════════════════════════════════════════════════════════════╗
║  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)                                  ║
║  │   ├── ✅ Clean Architecture                                 ║
║  │   ├── ✅ DI structure                                            ║
║  │   └── 🔄 API design review in progress...                     ║
║  └── 🎨 UX Designer review (parallel)                                ║
║      ├── ✅ CoUI compliance                                     ║
║      └── ⏳ Accessibility review waiting                          ║
║                                                                ║
║  Phase 4: IMPLEMENTATION ━━━━━━━━━━━━━━━━━━━━━━━━━━ ⏳         ║
║  └── Waiting (proceeds after Phase 3 completes)                 ║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

.claude/personas/ - 7 persona definitions
.claude/orchestrators/phase-gates.md - Phase gate details
.claude/skills/bmad/SKILL.md - BMAD skill definition
.claude/commands/product/bmad.md - BMAD command definition

BMAD Orchestrator

Architecture Overview#

Phase Structure#

Phase 1: Analysis#

Phase 2: Planning#

Phase 3: Solutioning#

Phase 4: Implementation#

Execution Flow#

Full Flow#

Phase Gate Handling#

On Gate Success#

On Gate Failure#

Parallel Execution Patterns#

Fan-out Pattern (Phase 3)#

Independent Task Parallelization (Phase 4)#

State Management#

Workflow State#

State Transitions#

Command Interface#

Start Full Workflow#

Individual Persona Review#

Status Check#

Manual Gate Verification#

Configuration#

settings.json Extension#

Output Format#

Progress Display#

Related Files#