BMAD-METHOD/docs/zh-cn/reference/workflow-map.md at cede485217bec817b50d6491df8e3a87deef8992

mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-08-28 19:20:41 +08:00

Files

T

Brian ee47e30cf6 refactor(bmad-ux): spine-based UX skill (DESIGN.md + EXPERIENCE.md) (#2413 )

* refactor(bmad-ux): replace bmad-create-ux-design with lean spine-based bmad-ux

* refactor(bmad-ux): adopt DESIGN.md spec, split into two-file spine, align prd/brief

DESIGN.md (visual identity per the Google Labs spec) and EXPERIENCE.md
(behavior, flow, IA) replace the single design.md spine. EXPERIENCE.md
cross-references DESIGN.md tokens via the spec's {path.to.token} syntax.

Example suite restructure
- 3 DESIGN.md examples: editorial (Stitch source / Linen & Logic), calm
  native mobile (Quill), shadcn-on-Tailwind web SaaS (Drift)
- 2 paired EXPERIENCE.md examples (Quill, Drift); Linen & Logic unpaired
  to model the Stitch handoff scenario
- Replaces the prior 2-example combined spine set

Discovery additions (outcome-driven, one line each)
- Source scan: glob {planning_artifacts}/ for candidates, parent never reads
- Form-factor: resolve before IA closes; journeys often derive it
- Surface closure: every stated need has a surface, every surface a journey
- Named-protagonist journeys (Mary, not "the user")
- Design handoff working mode (extensible producer registry, default: Stitch)

PRD and brief alignment with same insights
- bmad-prd: dropped standalone Primary Persona section from template;
  renamed "Personas + Journeys" entry to "Journey-led"; named-protagonist
  rule on UJs; form-factor probe; validation checklist updated
- bmad-product-brief: form-factor surfaced in Discovery topics

Quality scan fixes
- Added ## Overview heading; renamed ## Activation to ## On Activation
- Replaced ../ paths in example assets with {planning_artifacts}/
- Sources section compressed (abstract delta-only rule)
- Working mode aligned to "Fast path" / "Coaching path" BMad-wide convention

New
- references/design-md-spec.md: working summary of the spec for the LLM
- customize.toml: design_md_examples, experience_md_examples,
  design_handoffs registries
- .prettierignore: ignore .analysis/ quality-scan artifacts repo-wide

* refactor(bmad-ux): activation parity with prd/brief, opt-in reviewer gate, no headline grade

- Restructure On Activation as numbered six-step list mirroring bmad-prd
  and bmad-product-brief, restoring the explicit key-resolution list that
  earlier crammed-paragraph form had dropped (planning_artifacts and
  friends were silently unresolved at Create).
- Make Reviewer Gate opt-in and lens-selectable. At Finalize, ask before
  spending tokens on parallel reviewer subagents; at Validate intent,
  skip that question but still confirm lens picks. Stops the auto-run
  WCAG audit on hobby-stakes work.
- Drop the overall validation grade. Per-category verdicts and severity
  counts already say what is true; a single headline grade conflated
  design rigor with release readiness and led "POOR" pills landing on
  reports whose own bodies described the work as strong. Removed from
  references/validate.md (ladder rule + markdown twin), HTML template
  (grade pill div + CSS vars + classes).
- Trim creative-tools.md: drop the Custom entries section. Runtime
  prompt files should only carry what the LLM needs to act in this
  moment; how-to-extend-via-TOML is setup-time human documentation
  already covered by customize.toml comments.

* fix(bmad-ux): align validation report template with 8-category rubric

Template placeholders referenced 'Decision-readiness' and 'seven dimensions'
from the prior rubric. Replace with TEMPLATE_CATEGORY_NAME and inline the
eight canonical categories from references/validate.md so the synthesis pass
names them verbatim.

* fix(validate-skills): remove stale WF-01/WF-02 rules

WF-01/WF-02 were originally scoped to workflow.md files (now mostly gone)
but had been generalized to flag name/description in any non-SKILL.md
markdown. That over-captured legitimate spec files — e.g. DESIGN.md
examples in bmad-ux/assets/ that carry name/description per the Google
Labs DESIGN.md spec.

Step files are already covered by STEP-06. Rule count: 14 → 12.

* fix(bmad-ux): address PR review followups

- validation-report-template.html: severity badge class is badge-sev-*,
  not sev-* (the comment misled the synthesis pass).
- Sweep dangling bmad-create-ux-design references: module-help.csv,
  bmad-agent-ux-designer/customize.toml, bmad-prd/SKILL.md handoff list,
  workflow-map.md (en + 4 translations), getting-started.md (en + 4
  translations). Workflow-map output column updated to DESIGN.md +
  EXPERIENCE.md.
- references/validate.md: Markdown capitalized as a proper noun.

2026-05-22 23:16:06 -05:00

3.7 KiB

Raw Blame History

title, description, sidebar

title

description

sidebar

工作流地图

BMad Method 各阶段 workflow 与产出速查

order
1

BMad Method（BMM）通过分阶段 workflow 逐步构建上下文，让智能体始终知道“做什么、为什么做、如何做”。这张地图用于快速查阅阶段目标、关键 workflow 和对应产出。

如果你不确定下一步，优先运行 bmad-help。它会基于你当前项目状态和已安装模块给出实时建议。

在新标签页打开图表 ↗

阶段 1：分析（可选）

在正式规划前，先验证问题空间与关键假设。

Workflow	目的	产出
`bmad-brainstorming`	通过引导式创意方法扩展方案空间	`brainstorming-report.md`
`bmad-domain-research`、`bmad-market-research`、`bmad-technical-research`	验证领域、市场与技术假设	研究发现
`bmad-create-product-brief`	沉淀产品方向与战略愿景	`product-brief.md`

阶段 2：规划

定义“为谁做、做什么”。

Workflow	目的	产出
`bmad-create-prd`	明确 FR/NFR 与范围边界	`PRD.md`
`bmad-ux`	在 UX 复杂场景下补齐交互与体验方案	`DESIGN.md`, `EXPERIENCE.md`

阶段 3：解决方案设计（Solutioning）

定义“如何实现”并拆分可交付工作单元。

Workflow	目的	产出
`bmad-create-architecture`	显式记录技术决策与架构边界	`architecture.md`（含 ADR）
`bmad-create-epics-and-stories`	将需求拆分为可实施的 epics/stories	epics 文件与 story 条目
`bmad-check-implementation-readiness`	实施前 gate 检查	PASS / CONCERNS / FAIL 结论

阶段 4：实施

按 story 节奏持续交付与校验。

Workflow	目的	产出
`bmad-sprint-planning`	初始化迭代追踪（通常每项目一次）	`sprint-status.yaml`
`bmad-create-story`	准备下一个可实施 story	`story-[slug].md`
`bmad-dev-story`	按规范实现 story	可运行代码与测试
`bmad-code-review`	验证实现质量	通过或变更请求
`bmad-correct-course`	处理中途重大方向调整	更新后的计划或重路由
`bmad-sprint-status`	跟踪冲刺与 story 状态	状态更新
`bmad-retrospective`	epic 完成后复盘	经验与改进项

Quick Flow（并行快线）

当任务范围小且目标清晰时，可跳过阶段 1-3 直接推进：

Workflow	目的	产出
`bmad-quick-dev`	统一快流：意图澄清、规划、实现、审查、呈现	`spec-*.md` + 代码变更

上下文管理

每个阶段产出都会成为下一阶段输入：PRD 约束架构，架构约束开发，story 约束实现。没有这条链路，智能体更容易在跨 story 时出现不一致决策。

:::tip[Project Context 建议] 创建 project-context.md，把项目特有约定（技术栈、命名、组织、测试策略）写成共享规则，能显著降低实现偏差。 :::

创建方式：

手动创建：在 _bmad-output/project-context.md 记录项目规则
自动生成：运行 bmad-generate-project-context 从架构或代码库提取

3.7 KiB Raw Blame History Unescape Escape