Agent Skills › bacoco/BMad-Skills › bmad-architecture-design

bmad-architecture-design

GitHub

将已批准的PRD转化为技术架构设计，确定组件结构、技术选型及决策依据，生成ARCHITECTURE.md文档，为开发团队提供实施指导。

.claude/skills/bmad-architecture-design/SKILL.md bacoco/BMad-Skills

Trigger Scenarios

询问系统架构或技术栈提出如何进行系统设计提及技术决策或构建方案

Install

npx skills add bacoco/BMad-Skills --skill bmad-architecture-design -g -y

More Options

Non-standard path

npx skills add https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-architecture-design -g -y

Use without installing

npx skills use bacoco/BMad-Skills@bmad-architecture-design

指定 Agent (Claude Code)

npx skills add bacoco/BMad-Skills --skill bmad-architecture-design -a claude-code -g -y

安装 repo 全部 skill

npx skills add bacoco/BMad-Skills --all -g -y

预览 repo 内 skill

npx skills add bacoco/BMad-Skills --list

SKILL.md

Frontmatter

{
    "name": "bmad-architecture-design",
    "metadata": {
        "outputs": [
            "architecture-decisions",
            "system-design-doc",
            "tech-stack-rationale"
        ],
        "triggers": {
            "keywords": [
                "architecture",
                "design",
                "system",
                "build",
                "technical",
                "structure",
                "stack"
            ],
            "patterns": [
                "how should we build",
                "what's the architecture",
                "tech stack",
                "system design",
                "how to build this"
            ]
        },
        "auto-invoke": true,
        "capabilities": [
            "architecture-design",
            "tech-stack-selection",
            "system-design",
            "decision-documentation"
        ],
        "prerequisites": [
            "product-requirements-document"
        ]
    },
    "description": "Creates technical architecture and system design.",
    "allowed-tools": [
        "Read",
        "Write",
        "Grep"
    ]
}

Architecture Design 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)

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.

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.

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.

Quality Gates

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

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.