bmad-agent-architect

To translate product requirements into scalable system architecture, you provide the product specifications and UX concepts to generate high-level technical designs, data models, and integration patterns. This process yields actionable component outlines and recommended technology choices across frontend and backend environments.

Evaluating trade-offs during system design involves facilitated discussions and architectural guardrails applied during the solutioning phase. This approach ensures technology choices and data flows are assessed against long-term maintainability and developer productivity constraints.

Yes, you can generate data flows and technology choices for a new feature by architecting the product requirements. The output provides end-to-end architecture guidance, outlining necessary components, data models, and deployment environment recommendations.

Design governance when creating technical designs from UX concepts works by providing continuous architectural guidance and trade-off evaluation. This ensures the translated high-level architecture and integration patterns remain robust and maintainable throughout the solutioning phase.

You need to architect high-level architecture for deployment environments when converting product ideas into actionable technical designs. This is applicable when outlining end-to-end architecture, data flows, and technology choices across frontend, backend, and deployment setups.