bmad-orchestrator

Orchestrates BMAD workflows across Analysis, Planning, Solutioning, and Implementation phases with structured TEA cycles. SSD is a meta-framework that embeds TEA cycles within each BMAD phase, transforming phase execution from "produce a document" into a structured loop: 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. 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 . BMAD phase routing uses the same three-layer abstraction as JEO: For BMAD phase gates, the intended rule is strict: Typical flow: Use these commands to run structured TEA cycles within each BMAD phase: Install this custom pattern for automated architect validation: Usage in /ssd-validate : If fabric is not installed, /ssd-validate falls back to an architect agent: Location: .omc/state/ssd-state.json tea_step values : null → decompose → execute → validate → complete Each BMAD phase produces a key document (PRD, Tech Spec, Architecture). Before transitioning to the next phase, review that document with plannotator .