bmad-orchestrator
npx skills add https://github.com/supercent-io/skills-template --skill bmad-orchestrator
Agent 安装分布
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
Codex ì¬ì© ì°¸ê³
bmad-orchestratorì 기본 ì¤í ê²½ë¡ë Claude Codeì
ëë¤.
Codexìì ì§ì ëì¼í íë¦ì¼ë¡ ì¬ì©íë ¤ë©´ omx/ohmg ë± ìì ì¤ì¼ì¤í¸ë ì´ì
ê²½ë¡ë¥¼ íµí´ BMAD ë¨ê³ë¥¼ ì´ìíë ê²ì ê¶ì¥í©ëë¤.
BMAD Execution Commands
íë«í¼ë³ ì ì© ìí (íì¬ ì§ì 기ì¤)
| íë«í¼ | íì¬ ì§ì ë°©ì | ì ì© ì¡°ê±´ |
|---|---|---|
| Gemini CLI | ë¤ì´í°ë¸(ê¶ì¥) | bmad í¤ìë ë±ë¡ í /workflow-init ì¤í |
| Claude Code | ë¤ì´í°ë¸(ê¶ì¥) | ì¤í¬ ì¤ì¹ + 기ìµí´ í¨í´ |
| OpenCode | ì¤ì¼ì¤í¸ë ì´ì ì°ë | omx/ohmg/omx ë¥ ë¸ë¦¿ì§ ì¬ì© |
| Codex | ì¤ì¼ì¤í¸ë ì´ì ì°ë | omx/ohmgë¥ ë¸ë¦¿ì§ ì¬ì© |
íì¬ ì¤í¬ë§ì¼ë¡ ê°ë¥íì§:
- Gemini CLI/Claude Code: ê°ë¥
- OpenCode/Codex: ê°ë¥(ì¤ì¼ì¤í¸ë ì´ì ê²½ì )
Use these in your AI session:
/workflow-init
/workflow-status
Typical flow:
- Run
/workflow-initto bootstrap BMAD config. - Move through phases in order: Analysis -> Planning -> Solutioning -> Implementation.
- Run
/workflow-statusany 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 |