bmad-agent-architect

System architecture is defined by translating product requirements into explicit technical decisions and trade-offs. This process shapes implementation direction for web, API, and infrastructure layers while keeping delivery aligned with UX and PRD constraints.

Planning technical architecture for multi-tenant SaaS requires structured decision-making across web, API, authentication, and data layers. It produces actionable guidance that weighs pragmatic trade-offs to keep implementation aligned with product requirements.

Solution design review for product-to-engineering handoffs works by documenting architecture decisions that bridge UX direction and technical strategy. It ensures epics, PRDs, and delivery constraints remain consistent before development starts.

Implementation-readiness checks for API and authentication work are supported by applying structured decision-making. It validates that system architecture choices and technical strategy align with project context and product requirements.

System design requires explicit trade-offs to avoid abstract ideals and provide actionable guidance. Documenting these decisions during implementation planning ensures the technical architecture remains pragmatic and aligned with actual product constraints.