bmad-orchestrator - BMAD Workflow Orchestration Skill

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

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.

BMAD Execution Commands

Platform Support Status (Current)

| Platform | Current support mode | Requirements | |---|---|---| | Gemini CLI | Native (recommended) | Register the bmad keyword, then run /workflow-init | | Claude Code | Native (recommended) | Install skill + remember pattern | | OpenCode | Orchestration integration | Use an omx/ohmg/omx-style bridge | | Codex | Orchestration integration | Use an omx/ohmg-style bridge |

Possible with this skill alone:

Gemini CLI/Claude Code: Yes
OpenCode/Codex: Yes (via orchestration)

Use these in your AI session:

/workflow-init
/workflow-status

Typical flow:

Run /workflow-init to bootstrap BMAD config.
Move through phases in order: Analysis -> Planning -> Solutioning -> Implementation.
Run /workflow-status any time to inspect current phase and progress.

Quick Reference

| Action | Command | |--------|---------| | Initialize BMAD | /workflow-init | | Check BMAD status | /workflow-status |

plannotator Integration (Phase Review Gate)

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.

Why use plannotator with BMAD?

Quality gate: Approve or request changes before locking in a phase deliverable
Obsidian archive: Every approved phase document auto-saves with YAML frontmatter and [[BMAD Plans]] backlink
Team visibility: Share a plannotator link so stakeholders can annotate the PRD/Architecture before implementation begins

Phase Review Pattern

After completing any phase document, submit it for review:

# After /prd → docs/prd-myapp-2026-02-22.md is created
bash scripts/phase-gate-review.sh docs/prd-myapp-2026-02-22.md "PRD Review: myapp"

# After /architecture → docs/architecture-myapp-2026-02-22.md is created
bash scripts/phase-gate-review.sh docs/architecture-myapp-2026-02-22.md "Architecture Review: myapp"

Or submit the plan directly from within your AI session:

# In Claude Code after /prd completes:
planno — review the PRD before we proceed to Phase 3

The agent will call submit_plan with the document content, opening the plannotator UI for review.

Phase Gate Flow

/prd completes → docs/prd-myapp.md created
       ↓
 bash scripts/phase-gate-review.sh docs/prd-myapp.md
       ↓
 plannotator UI opens in browser
       ↓
  [Approve]              [Request Changes]
       ↓                        ↓
 Obsidian saved          Agent revises doc
 bmm-workflow-status     Re-submit for review
 updated automatically
       ↓
 /architecture (Phase 3)

Obsidian Save Format

Approved phase documents are saved to your Obsidian vault with:

---
created: 2026-02-22T22:45:30.000Z
source: plannotator
tags: [bmad, phase-2, prd, myapp]
---

[[BMAD Plans]]

# PRD: myapp
...

Quick Reference

| Phase | Document | Gate Command | |-------|----------|--------------| | Phase 1 → 2 | Product Brief | bash scripts/phase-gate-review.sh docs/product-brief-*.md | | Phase 2 → 3 | PRD / Tech Spec | bash scripts/phase-gate-review.sh docs/prd-*.md | | Phase 3 → 4 | Architecture | bash scripts/phase-gate-review.sh docs/architecture-*.md | | Phase 4 done | Sprint Plan | bash scripts/phase-gate-review.sh docs/sprint-status.yaml |

Agent Skills: bmad-orchestrator - BMAD Workflow Orchestration

Install this agent skill to your local

Skill Files