bmad-orchestrator

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 should be treated with the same three-layer abstraction used by JEO: For BMAD phase gates, the intended rule is strict: Possible with this skill alone : Use these in your AI session: Typical flow: Each BMAD phase produces a key document (PRD, Tech Spec, Architecture). Before transitioning to the next phase, review that document with plannotator and auto-save it to Obsidian. After completing any phase document, submit it for review: Or submit the plan directly from within your AI session: The agent will open the plannotator UI for review. In Claude Code: call EnterPlanMode → write plan → call ExitPlanMode (hook fires automatically). In OpenCode: the submit_plan plugin tool is available directly. Approved phase documents are saved to your Obsidian vault with: - 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 - 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"...