bmad-orchestrator — BMAD Workflow Orchestration with SSD

When to use this skill

• Initializing BMAD in a new project (with or without SSD)
• Running structured TEA cycles within each BMAD phase
• Checking and resuming BMAD/SSD workflow status
• Routing work across Analysis, Planning, Solutioning, and Implementation
• Managing structured handoff and cross-phase traceability between phases

What is SSD (Structured System Design)?

SSD is a meta-framework that embeds TEA cycles within each BMAD phase, transforming phase execution from "produce a document" into a structured loop:

T → Task:     Decompose the phase into concrete tasks with assigned agents
E → Execute:  Run tasks in parallel via multi-agent team execution
A → Architect: Validate outputs for coherence, completeness, and cross-phase traceability

Each BMAD phase becomes an independent TEA cycle. The architect validation step produces a PASS, PASS_WITH_WARNINGS, REVISE, or FAIL verdict. Only after PASS (or PASS_WITH_WARNINGS) does the human review gate (plannotator) open. This ensures automated structural correctness before human review.

SSD vs. Standard BMAD

Installation

npx skills add https://github.com/akillness/oh-my-skills --skill bmad-orchestrator

Notes for Codex Usage

bmad-orchestrator's default execution path is Claude Code. To run the same flow directly in Codex, we recommend operating BMAD stages via a higher-level orchestration path such as omx/ohmg.

Control Model

BMAD phase routing uses the same three-layer abstraction as JEO:

• settings: platform-specific runtime configuration such as Claude hooks, Codex/Gemini instructions, and MCP setup
• rules: phase constraints such as "do not advance before the current phase document is approved" and "do not reopen the same unchanged phase document for review"
• hooks: platform callbacks such as Claude ExitPlanMode, Codex notify, or Gemini AfterAgent

For BMAD phase gates, the intended rule is strict:

• Review the current phase document before moving forward
• If the document hash has not changed since the last terminal review result, do not relaunch plannotator
• Only a revised document resets the gate and permits another review cycle
• With SSD: plannotator gate requires architect_verdict: "PASS" or "PASS_WITH_WARNINGS" in ssd-state.json before opening

Platform Support Status

Standard BMAD Commands

/workflow-init [--ssd]
/workflow-status

Typical flow:

1. Run /workflow-init to bootstrap BMAD config (add --ssd to also initialize SSD state).
2. Move through phases: Analysis → Planning → Solutioning → Implementation.
3. Run /workflow-status any time to inspect current phase and progress.

SSD Commands (TEA Integration)

Use these commands to run structured TEA cycles within each BMAD phase:

SSD Full Flow

/workflow-init --ssd
       |
       v
  ┌─────────────────────────────────────────────────────┐
  │              PHASE N TEA CYCLE                      │
  │                                                     │
  │  /ssd-decompose  (or /ssd-cycle for full auto)      │
  │       |                                             │
  │       v                                             │
  │  [T] Task decomposition                             │
  │       planner/analyst produces task list            │
  │       → ssd-state.json phases[N].tasks updated      │
  │       |                                             │
  │       v                                             │
  │  /ssd-execute                                       │
  │       |                                             │
  │       v                                             │
  │  [E] Multi-agent execution via /team                │
  │       TeamCreate → TaskCreate per subtask           │
  │       Agents: executor, analyst, designer,          │
  │               test-engineer, security-reviewer…     │
  │       → docs/ssd/phase-N/ artifacts produced        │
  │       → Phase document assembled from artifacts     │
  │       |                                             │
  │       v                                             │
  │  /ssd-validate                                      │
  │       |                                             │
  │       v                                             │
  │  [A] Architect validation                           │
  │       fabric -p bmad_ssd_phase_review               │
  │       (fallback: architect agent via TaskCreate)    │
  │       |                                             │
  │       ├── PASS ──────────→ plannotator review       │
  │       │                         |                   │
  │       │                    ┌────┴────┐              │
  │       │                    │ Approve │ Req Changes  │
  │       │                    └────┬────┘     |        │
  │       │                         |     Loop to [E]   │
  │       │                         v     with feedback │
  │       │                    /ssd-advance              │
  │       │                    → phase N+1               │
  │       │                                             │
  │       ├── PASS_WITH_WARNINGS → plannotator (warned) │
  │       │                                             │
  │       ├── REVISE → targeted re-execute specific     │
  │       │             tasks, then re-validate         │
  │       │                                             │
  │       └── FAIL → full re-execute with changes,      │
  │                   then re-validate                  │
  │                   (max 3 cycles, then escalate)     │
  └─────────────────────────────────────────────────────┘

TEA Per-Phase Mapping

Phase 1: Analysis

Phase 2: Planning

Phase 3: Solutioning

Phase 4: Implementation

Fabric Pattern: bmad_ssd_phase_review

Install this custom pattern for automated architect validation:

mkdir -p ~/.config/fabric/patterns/bmad_ssd_phase_review
cat > ~/.config/fabric/patterns/bmad_ssd_phase_review/system.md << 'EOF'
# IDENTITY AND PURPOSE

You are an expert system architect performing a structured phase review for the BMAD Structured System Design (SSD) framework. Your job is to validate that a phase document is internally coherent, externally consistent with prior phase artifacts, and complete enough to advance to the next phase.

Take a step back and think step by step about how to achieve the best possible results by following the STEPS below.

# STEPS

1. IDENTIFY the current BMAD phase (Analysis, Planning, Solutioning, Implementation) from the input metadata.

2. PARSE the phase document and extract all claims, requirements, design decisions, and deliverables.

3. INTERNAL COHERENCE CHECK:
   - Are there contradictory statements within the document?
   - Are all sections complete (no TODOs, placeholders, or TBDs)?
   - Do quantitative claims have justification?

4. CROSS-PHASE TRACEABILITY CHECK (if prior phase artifacts are provided):
   - Phase 2 (Planning): Does every PRD requirement trace to a product brief goal?
   - Phase 3 (Solutioning): Does the architecture address every PRD functional requirement?
   - Phase 4 (Implementation): Does every story map to an architecture component?
   - Flag any orphaned items.

5. COMPLETENESS CHECK against BMAD level expectations:
   - Level 0-1: Minimal viable coverage
   - Level 2: Full requirement coverage with acceptance criteria
   - Level 3: Comprehensive with integration points and risk analysis
   - Level 4: Enterprise-grade with security, performance, and infrastructure coverage

6. RISK ASSESSMENT:
   - Identify assumptions that could invalidate the phase output
   - Flag unresolved dependencies
   - Note scope creep relative to prior phase boundaries

7. PRODUCE a structured verdict.

# OUTPUT INSTRUCTIONS

- Output valid Markdown only.
- Begin with a `## Verdict` section: one of `PASS`, `PASS_WITH_WARNINGS`, `FAIL`, or `REVISE`.
- Follow with `## Internal Coherence` (findings with line references).
- Follow with `## Cross-Phase Traceability` (coverage matrix if applicable).
- Follow with `## Completeness` (missing sections or underspecified areas).
- Follow with `## Risks` (ranked by severity: critical, high, medium, low).
- Follow with `## Required Changes` (concrete, actionable items if verdict is FAIL or REVISE).
- Do not include warnings, disclaimers, or caveats outside the structured sections.

# INPUT

INPUT:
EOF

Usage in /ssd-validate:

# Pipe current phase doc + prior artifacts for cross-phase validation
{
  echo "--- CURRENT PHASE DOCUMENT ---"
  cat "$CURRENT_DOC"
  echo "--- PRIOR PHASE ARTIFACTS ---"
  for prior in "${PRIOR_DOCS[@]}"; do
    echo "--- $(basename "$prior") ---"
    cat "$prior"
  done
} | fabric -p bmad_ssd_phase_review --stream > docs/ssd/phase-N/architect-review.md