bmad-orchestrator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

bmad-orchestrator - BMAD Workflow Orchestration

bmad-orchestrator - BMAD工作流编排

When to use this skill

何时使用此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

在新项目中初始化BMAD
检查并恢复BMAD工作流状态
在分析、规划、方案设计与实施阶段之间分配工作
管理各阶段间的结构化交接

Installation

安装

bash

npx skills add https://github.com/supercent-io/skills-template --skill bmad-orchestrator

bash

npx skills add https://github.com/supercent-io/skills-template --skill bmad-orchestrator

Codex 사용 참고

Codex使用参考

bmad-orchestrator

의 기본 실행 경로는 Claude Code입니다.
Codex에서 직접 동일한 흐름으로 사용하려면

omx

ohmg

등 상위 오케스트레이션 경로를 통해 BMAD 단계를 운영하는 것을 권장합니다.

bmad-orchestrator

的默认执行渠道是Claude Code。
若要在Codex中直接以相同流程使用，建议通过

omx

ohmg

等上层编排渠道来运行BMAD阶段任务。

BMAD Execution Commands

BMAD执行命令

플랫폼별 적용 상태 (현재 지원 기준)

各平台适用状态（当前支持标准）

플랫폼	현재 지원 방식	적용 조건
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:

text

/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.

平台	当前支持方式	适用条件
Gemini CLI	原生（推荐）	注册 `bmad` 关键词后执行 `/workflow-init`
Claude Code	原生（推荐）	安装Skill + 使用「记住」模式
OpenCode	编排联动	使用 `omx` / `ohmg` 类桥接工具
Codex	编排联动	使用 `omx` / `ohmg` 类桥接工具

仅当前Skill是否可用：

Gemini CLI/Claude Code：是
OpenCode/Codex：是（通过编排渠道）

在AI会话中使用以下命令：

text

/workflow-init
/workflow-status

典型流程：

运行
```
/workflow-init
```
来初始化BMAD配置。
按顺序推进各阶段：分析 → 规划 → 方案设计 → 实施。
随时运行
```
/workflow-status
```
来查看当前阶段与进度。

Quick Reference

快速参考

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

操作	命令
初始化BMAD	`/workflow-init`
查看BMAD状态	`/workflow-status`

plannotator Integration (Phase Review Gate)

plannotator集成（阶段评审关卡）

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.

每个BMAD阶段都会生成一份关键文档（PRD、技术规格书、架构文档）。在进入下一阶段前，需使用plannotator评审该文档并自动保存至Obsidian。

Why use plannotator with BMAD?

为何在BMAD中使用plannotator？

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

质量关卡：在锁定阶段交付成果前，批准或要求修改
Obsidian归档：所有已批准的阶段文档会自动保存，并附带YAML前置元数据和
```
[[BMAD Plans]]
```
反向链接
团队可见性：分享plannotator链接，让利益相关者在实施开始前就能对PRD/架构文档进行批注

Phase Review Pattern

阶段评审模式

After completing any phase document, submit it for review:

bash

undefined

完成任一阶段文档后，提交评审：

bash

undefined

After /prd → docs/prd-myapp-2026-02-22.md is created

执行/prd后 → 生成docs/prd-myapp-2026-02-22.md

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

bash scripts/phase-gate-review.sh docs/prd-myapp-2026-02-22.md "PRD评审：myapp"

After /architecture → docs/architecture-myapp-2026-02-22.md is created

执行/architecture后 → 生成docs/architecture-myapp-2026-02-22.md

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:

```text

bash scripts/phase-gate-review.sh docs/architecture-myapp-2026-02-22.md "架构评审：myapp"


或直接在AI会话中提交方案：

```text

In Claude Code after /prd completes:

在Claude Code中完成/prd后：

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.

planno — 进入第3阶段前先评审PRD


Agent会调用`submit_plan`接口传入文档内容，打开plannotator UI进行评审。

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)

/prd完成 → 生成docs/prd-myapp.md
       ↓
执行bash scripts/phase-gate-review.sh docs/prd-myapp.md
       ↓
浏览器中打开plannotator UI
       ↓
  [批准]              [要求修改]
       ↓                        ↓
保存至Obsidian          Agent修订文档
自动更新bmm-workflow-status     重新提交评审
       ↓
进入/architecture（第3阶段）

Obsidian Save Format

Obsidian保存格式

Approved phase documents are saved to your Obsidian vault with:

yaml

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

[[BMAD Plans]]

已批准的阶段文档会保存至你的Obsidian库，格式如下：

yaml

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

[[BMAD Plans]]

PRD: myapp

...

undefined

...

undefined

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`

阶段	文档	关卡命令
第1阶段→第2阶段	产品简报	`bash scripts/phase-gate-review.sh docs/product-brief-*.md`
第2阶段→第3阶段	PRD / 技术规格书	`bash scripts/phase-gate-review.sh docs/prd-*.md`
第3阶段→第4阶段	架构文档	`bash scripts/phase-gate-review.sh docs/architecture-*.md`
第4阶段完成	迭代计划	`bash scripts/phase-gate-review.sh docs/sprint-status.yaml`