bmad-architecture-design

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Architecture Design Skill

架构设计Skill

When to Invoke

触发时机

Automatically activate when user:

Says "How should we build this?", "What's the architecture?"
Asks "Tech stack?", "System design?", "How to architect?"
Mentions "architecture", "technical decisions", "stack"
PRD and epics are approved (Phase 3)
Uses words like: architecture, tech stack, design, system, build, technical

Specific trigger phrases:

"How should we build this?"
"What's the architecture?"
"Choose tech stack"
"System design for [project]"
"Technical architecture"
"How to architect [feature]"

Prerequisites:

PRD exists and approved
Epics defined

Do NOT invoke when:

PRD not ready (use bmad-product-planning first)
Already have architecture (skip to stories)
Simple Level 0-1 project (may not need formal architecture)

当用户出现以下情况时自动激活：

询问“我们应该如何构建这个？”、“架构是什么？”
询问“技术栈？”、“系统设计？”、“如何进行架构设计？”
提及“架构”、“技术决策”、“技术栈”
PRD和epics已获批（第三阶段）
使用以下词汇：architecture、tech stack、design、system、build、technical

具体触发短语：

“我们应该如何构建这个？”
“架构是什么？”
“选择技术栈”
“[项目]的系统设计”
“技术架构”
“如何设计[功能]的架构”

前置条件：

PRD已存在且获批
Epics已定义

以下情况请勿触发：

PRD未就绪（请先使用bmad-product-planning）
已有架构（直接进入用户故事环节）
简单的0-1级项目（可能不需要正式架构）

Mission

任务目标

Convert approved product requirements into a Decision Architecture that communicates component structure, technology choices, and rationale for implementation teams.

将获批的产品需求转化为决策架构，向实施团队传达组件结构、技术选择及决策依据。

Inputs Required

所需输入

prd: latest PRD plus epic roadmap from product-requirements skill
constraints: non-functional requirements, compliance rules, and integrations
existing_assets: repositories, current architecture diagrams, or technology standards
project_level: BMAD level sizing to guide depth of design

Missing inputs must be escalated to the orchestrator or originating skill before work proceeds.

prd：来自product-requirements skill的最新PRD及epic路线图
constraints：非功能性需求、合规规则及集成要求
existing_assets：代码仓库、当前架构图或技术标准
project_level：BMAD规模等级，用于指导设计深度

若存在缺失的输入，必须在开展工作前上报给编排器或源skill。

Outputs

输出成果

ARCHITECTURE.md

written using

assets/decision-architecture-template.md.template

Updated risk and decision log entries summarized for stakeholders

Deliverables should highlight decisions, rejected options, and implementation guardrails.

使用

assets/decision-architecture-template.md.template

模板编写的

ARCHITECTURE.md

文档

为利益相关者汇总更新的风险与决策日志条目

交付成果应突出决策内容、被否决的方案及实施约束条件。

Process

执行流程

Validate prerequisites via
```
CHECKLIST.md
```
and confirm planning artifacts are approved.
Identify architecture drivers (quality attributes, constraints, integrations).
Design component topology, data flows, and technology selections with traceability to requirements.
Record key decisions, alternatives, and mitigation strategies.
Generate or update architecture artifact using
```
scripts/generate_architecture.py
```
if structured data is available.
Review the quality checklist and publish summary plus follow-up actions for delivery-planning and development-execution skills.

通过
```
CHECKLIST.md
```
验证前置条件，确认规划工件已获批。
确定架构驱动因素（质量属性、约束条件、集成要求）。
设计组件拓扑、数据流及技术选型，并与需求建立可追溯性关联。
记录关键决策、备选方案及风险缓解策略。
若有结构化数据，使用
```
scripts/generate_architecture.py
```
生成或更新架构工件。
审核质量检查清单，发布摘要及后续行动项，供delivery-planning和development-execution skills使用。

Quality Gates

质量关卡

CHECKLIST.md

to ensure completeness, feasibility, and stakeholder alignment. Stop if guardrails fail.

遵循

CHECKLIST.md

确保内容完整、方案可行且与利益相关者达成一致。若未通过约束检查，需停止工作。

Error Handling

错误处理

When contradictions or gaps exist:

Cite the specific requirement or assumption causing the conflict.
Request clarifications from product-requirements, UX, or discovery-analysis skills.
Recommend holding implementation until resolution is documented.

当存在矛盾或缺口时：

明确指出导致冲突的具体需求或假设。
向product-requirements、UX或discovery-analysis skills请求澄清。
建议在问题解决并形成文档前暂停实施。