bmad-agent-architect

To translate product requirements and UX into technical architecture, you provide your PRD and UX details to generate concrete architecture decisions, rationale, and trade-offs across frontend, backend, data, and deployment layers.

Documenting architecture trade-offs during a design review involves analyzing your PRD constraints to produce structured rationale, technology stack recommendations, and high-level design patterns that reduce engineering risk.

An architect turns a PRD into deployment considerations by mapping product constraints against system architecture options, delivering structured trade-offs, stack recommendations, and implementation guidance for engineering teams.

Yes, you can use this for frontend, backend, and data architecture planning simultaneously, as it evaluates trade-offs and produces unified architecture decisions aligned with your PRD across all these layers.

You need a system architecture review for your product ideas during early design discussions or when translating fuzzy requirements into actionable technical plans to reduce risk and accelerate engineering delivery.

Generating architecture rationale instead of just picking a stack ensures your technology choices are explicitly aligned with PRD constraints, documenting trade-offs that guide engineering work and mitigate project risks.