bmad-architecture

Translate requirements into architecture by structuring technology decisions, system design, and implementation patterns into a documented architecture. This Skill generates ARCHITECTURE.md from PRDs and epics, mapping decisions to affected features, recording alternatives and rationale, and defining guardrails for consistent development.

Architecture documentation should capture key decisions, affected epics, considered alternatives, implementation rationale, and guardrails. This Skill embeds decision logs with trade-off analysis, technology justifications, security considerations, and project structure guidance to align development teams on technical choices.

Select technology by evaluating frameworks, databases, and build tools against project requirements, scalability needs, and constraints. This Skill recommends and justifies core technologies based on PRD scope, defining API contracts, naming conventions, error handling patterns, and providing structured rationale for each choice.

Yes, this Skill defines API contracts, security considerations, and implementation patterns as part of comprehensive architecture design. It generates structured documentation of integration points, data flows, and guardrails for secure, maintainable development aligned with business goals.

This Skill applies to Phase 3 solutioning where approved requirements guide architecture across topology, data flows, and integration points. It works equally for backend API design and broader system architecture, as long as PRDs, epics, and constraints are available to structure technology and implementation decisions.

Yes, approved PRD, epics, constraints, and assets are prerequisite inputs. This Skill translates these into structured architecture design, so having finalized requirements, decision criteria, and business context available upfront ensures the generated ARCHITECTURE.md aligns development with approved product scope.