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.
1---2name: bmad-architecture-design3description: Creates technical architecture and system design.4---5
6# Architecture Design Skill
7
8## When to Invoke
9
10**Automatically activate when user:**
11- Says "How should we build this?", "What's the architecture?"
12- Asks "Tech stack?", "System design?", "How to architect?"
13- Mentions "architecture", "technical decisions", "stack"
14- PRD and epics are approved (Phase 3)
15- Uses words like: architecture, tech stack, design, system, build, technical
16
17**Specific trigger phrases:**
18- "How should we build this?"
19- "What's the architecture?"
20- "Choose tech stack"
21- "System design for [project]"
22- "Technical architecture"
23- "How to architect [feature]"
24
25**Prerequisites:**
26- PRD exists and approved
27- Epics defined
28
29**Do NOT invoke when:**
30- PRD not ready (use bmad-product-planning first)
31- Already have architecture (skip to stories)
32- Simple Level 0-1 project (may not need formal architecture)
33
34## Mission
35Convert approved product requirements into a Decision Architecture that communicates component structure, technology choices, and rationale for implementation teams.
36
37## Inputs Required
38- prd: latest PRD plus epic roadmap from product-requirements skill
39- constraints: non-functional requirements, compliance rules, and integrations
40- existing_assets: repositories, current architecture diagrams, or technology standards
41- project_level: BMAD level sizing to guide depth of design
42
43Missing inputs must be escalated to the orchestrator or originating skill before work proceeds.
44
45## Outputs
46- `ARCHITECTURE.md` written using `assets/decision-architecture-template.md.template`
47- Updated risk and decision log entries summarized for stakeholders
48
49Deliverables should highlight decisions, rejected options, and implementation guardrails.
50
51## Process
521. Validate prerequisites via `CHECKLIST.md` and confirm planning artifacts are approved.
532. Identify architecture drivers (quality attributes, constraints, integrations).
543. Design component topology, data flows, and technology selections with traceability to requirements.
554. Record key decisions, alternatives, and mitigation strategies.
565. Generate or update architecture artifact using `scripts/generate_architecture.py` if structured data is available.
576. Review the quality checklist and publish summary plus follow-up actions for delivery-planning and development-execution skills.
58
59## Quality Gates
60Follow `CHECKLIST.md` to ensure completeness, feasibility, and stakeholder alignment. Stop if guardrails fail.
61
62## Error Handling
63When contradictions or gaps exist:
64- Cite the specific requirement or assumption causing the conflict.
65- Request clarifications from product-requirements, UX, or discovery-analysis skills.
66- Recommend holding implementation until resolution is documented.
majiayu000