bmad-orchestratorlisted

# bmad-orchestrator - BMAD Workflow Orchestration ## When to use this skill - Initializing BMAD in a new project - Checking and resuming BMAD workflow status - Routing work across Analysis, Planning, Solutioning, and Implementation - Managing structured handoff between phases --- ## Installation ```bash npx skills add https://github.com/supercent-io/skills-template --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 should be treated with the same three-layer abstraction used by 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 --- ## BMAD Execution Commands ## Platform Support Status (Current) | Platform | Current