bmad

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

bmad - BMAD Workflow Orchestration

bmad - 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

bash

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

Notes for Codex Usage

Codex使用注意事项

bmad

'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

的默认执行路径是Claude Code。要直接在Codex中运行相同流程，我们建议通过更上层的编排路径（例如

omx

ohmg

）来操作BMAD阶段。

Control Model

控制模型

BMAD phase routing should be treated with the same three-layer abstraction used by OMG:

```
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阶段路由应采用与OMG相同的三层抽象：

```
settings
```
：平台特定的运行时配置，例如Claude钩子、Codex/Gemini指令以及MCP设置
```
rules
```
：阶段约束，例如「当前阶段文档获批前不得推进」和「不得重新打开未修改的同一份阶段文档进行评审」
```
hooks
```
：平台回调，例如Claude
```
ExitPlanMode
```
、Codex
```
notify
```
或Gemini
```
AfterAgent
```

BMAD阶段关卡的预设规则十分严格：

推进到下一阶段前必须评审当前阶段文档
如果自上次最终评审结果以来文档哈希未发生变化，不要重新启动plannotator
只有修订后的文档才能重置关卡并允许开启新一轮评审

BMAD Execution Commands

BMAD执行命令

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:

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 + `remember` 模式
OpenCode	编排集成	使用 `omx` / `ohmg` / `omx` 风格的桥接层
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"

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 "Architecture Review: 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 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.

planno — review the PRD before we proceed to Phase 3


Agent会打开plannotator UI供评审。在Claude Code中：调用`EnterPlanMode` → 编写计划 → 调用`ExitPlanMode`（钩子自动触发）。在OpenCode中：可直接使用`submit_plan`插件工具。

Phase Gate Flow

阶段关卡流程

/prd completes → docs/prd-myapp.md created
       ↓
 bash scripts/phase-gate-review.sh docs/prd-myapp.md
       ↓
 hash guard checks whether this exact document was already reviewed
       ↓
 unchanged hash? yes → keep previous terminal result, do not reopen UI
       ↓ no
 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
       ↓
 哈希防护检查该文档是否已经过评审
       ↓
 哈希未变更？是 → 保留之前的最终结果，不重新打开UI
       ↓ 否
 plannotator UI在浏览器中打开
       ↓
  [批准]              [请求修改]
       ↓                        ↓
 保存到Obsidian          Agent修订文档
 bmm-workflow-status        重新提交评审
 自动更新
       ↓
 /architecture（第三阶段）

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`

TEA Integration (Test Architect)

TEA集成（测试架构师）

TEA (Test Architect) is an official BMAD v6 external module providing enterprise-grade test strategy and quality gates across all phases. See

resources/tea-workflows.md

for full workflow reference.

TEA（Test Architect）是BMAD v6的官方外部模块，可为所有阶段提供企业级测试策略和质量关卡。完整工作流参考请见

resources/tea-workflows.md

。

TEA Integration Points

TEA集成点

Phase	TEA Workflow	Command	Level
Phase 2: Planning	NFR Assessment	`/tea-nfr`	Level 3+ required
Phase 3: Solutioning	Test Design	`/tea-test-design`	Level 2+ recommended
Phase 3: Solutioning	Framework Setup	`/tea-framework`	Level 2+ recommended
Phase 3: Solutioning	CI Integration	`/tea-ci`	Level 2+ recommended
Phase 4: Implementation	ATDD	`/tea-atdd`	Per epic
Phase 4: Implementation	Test Automation	`/tea-automate`	Per epic
Phase 4: Implementation	Test Review	`/tea-review`	Level 2+ required
Phase 4: Implementation	Requirements Tracing	`/tea-trace`	Level 3+ required
Release Gate	Go/No-Go Decision	`/tea-release-gate`	Level 2+ required

阶段	TEA工作流	命令	级别
阶段2：规划	非功能需求评估	`/tea-nfr`	要求Level 3+
阶段3：方案设计	测试设计	`/tea-test-design`	推荐Level 2+
阶段3：方案设计	框架搭建	`/tea-framework`	推荐Level 2+
阶段3：方案设计	CI集成	`/tea-ci`	推荐Level 2+
阶段4：实施	验收测试驱动开发	`/tea-atdd`	每个史诗级需求执行
阶段4：实施	测试自动化	`/tea-automate`	每个史诗级需求执行
阶段4：实施	测试评审	`/tea-review`	要求Level 2+
阶段4：实施	需求追溯	`/tea-trace`	要求Level 3+
发布关卡	上线/回滚决策	`/tea-release-gate`	要求Level 2+

TEA Risk Prioritization

TEA风险优先级

TEA uses risk-based test prioritization: P0 (critical) → P1 (high) → P2 (medium) → P3 (low), calculated from probability × impact.

TEA采用基于风险的测试优先级：P0（极严重）→ P1（高）→ P2（中）→ P3（低），优先级由发生概率 × 影响范围计算得出。

SSD — Spec-Driven Development Path

SSD — 规范驱动开发路径

SSD (Spec-Driven Development) enforces a spec-first approach: formal machine-readable specifications must be created in Phase 2 before Architecture work begins.

SSD（Spec-Driven Development）推行规范优先的开发方式：必须在第2阶段创建正式的机器可读规范，之后才能开始架构工作。

SSD Workflow Commands

SSD工作流命令

Command	Output	When
`/spec-openapi`	OpenAPI 3.x spec (docs/spec-openapi-*.yaml)	API projects, Phase 2
`/spec-schema`	JSON Schema definitions (docs/spec-schema-*.json)	Data-heavy projects, Phase 2
`/spec-bdd`	Gherkin feature files (docs/stories/*.feature)	All Phase 4 stories

命令	输出	使用场景
`/spec-openapi`	OpenAPI 3.x规范（docs/spec-openapi-*.yaml）	API项目，阶段2
`/spec-schema`	JSON Schema定义（docs/spec-schema-*.json）	数据密集型项目，阶段2
`/spec-bdd`	Gherkin功能文件（docs/stories/*.feature）	所有阶段4的需求故事

SSD Workflow Path (Level 2+)

SSD工作流路径（Level 2+）

Phase 2: PRD → /spec-openapi or /spec-schema → plannotator gate
Phase 3: Architecture (references spec) → /spec-bdd scenarios
Phase 4: Dev Story implements spec + passes BDD scenarios

阶段2：PRD → /spec-openapi或/spec-schema → plannotator关卡
阶段3：架构（引用规范） → /spec-bdd场景
阶段4：开发需求实现规范 + 通过BDD场景验证

SSD in Tech Spec (Level 0-1)

技术规范中的SSD（Level 0-1）

For smaller projects, embed specs inline:

Include API contract section in Tech Spec
Define acceptance criteria as Given/When/Then scenarios
Reference spec file path in story blockedBy

小型项目可直接内嵌规范：

在技术规范中加入API契约章节
用Given/When/Then场景定义验收标准
在需求的blockedBy字段中引用规范文件路径

Fabric Pattern Integration

Fabric模式集成

Use fabric CLI to analyze and improve BMAD phase documents at each gate.

使用fabric CLI在每个关卡分析并优化BMAD阶段文档。

Per-Phase Fabric Commands

各阶段Fabric命令

bash

undefined

bash

undefined

Phase 1 — Extract insights from product brief

阶段1 — 从产品概要中提取洞察

cat docs/product-brief-*.md | fabric -p analyze_paper --stream

Phase 2 — Review PRD for completeness

阶段2 — 评审PRD完整性

cat docs/prd-*.md | fabric -p extract_wisdom --stream

Phase 3 — Summarize architecture decisions

阶段3 — 汇总架构决策

cat docs/architecture-*.md | fabric -p create_summary

Phase 4 — Explain implementation changes

阶段4 — 解释实现变更

git diff HEAD~1 | fabric -p explain_code

Improve any phase document before review

评审前优化任意阶段文档

cat docs/prd-*.md | fabric -p improve_writing > docs/prd-improved.md

undefined

cat docs/prd-*.md | fabric -p improve_writing > docs/prd-improved.md

undefined

Integration with plannotator Gate

plannotator关卡集成

Before submitting a document to plannotator for phase gate review, run fabric to improve it:

bash

undefined

提交文档到plannotator进行阶段关卡评审前，先运行fabric优化：

bash

undefined

Run fabric improvement, then gate review

运行fabric优化，再提交关卡评审

cat docs/architecture-*.md | fabric -p improve_writing > /tmp/arch-improved.md bash scripts/phase-gate-review.sh /tmp/arch-improved.md "Architecture Review"


See `resources/fabric-patterns.md` for complete pattern reference.

cat docs/architecture-*.md | fabric -p improve_writing > /tmp/arch-improved.md bash scripts/phase-gate-review.sh /tmp/arch-improved.md "Architecture Review"


完整模式参考请见`resources/fabric-patterns.md`。