LogoSkills

BMAD Orchestrator

BMAD framework main orchestrator

항ëŠĐë‚īėšĐ
Version1.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#

ItemContent
Responsible PersonaAnalyst
PurposeRequirements analysis, Acceptance Criteria definition, feasibility review
InputTask description (text)
OutputAnalyzed requirements, Acceptance Criteria list
GateRequirements clarity, scope appropriateness, Acceptance Criteria testability

Phase 2: Planning#

ItemContent
Responsible PersonaProduct Manager
PurposeIssue structuring, Story Point estimation, priority setting
InputPhase 1 output
OutputCreated issues, labels, dependencies
GateEpic/Story structure, Story Point, labeling, dependencies

Phase 3: Solutioning#

ItemContent
Responsible PersonaArchitect + UX Designer (parallel)
PurposeArchitecture design, UI/UX review
InputPhase 2 output
OutputDesign document, UI guidelines
GateClean Architecture, DI structure, CoUI compliance, accessibility

Phase 4: Implementation#

ItemContent
Responsible PersonaFlutter Dev + Backend Dev + Scrum Master
PurposeCode implementation, testing, PR creation, merge
InputPhase 3 output
OutputCompleted code, tests, PR
GateLint 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 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
/bmad  " task description " 

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

Individual Persona Review#

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

Status Check#

# Check overall status
/bmad:status

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

Manual Gate Verification#

# Manual gate verification
/bmad: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/bmad.md - BMAD command definition