bmad-agent-architect

Scalable system architecture for distributed systems is designed by translating user goals and constraints into shippable infrastructure decisions. This skill guides pragmatic technology selection and documents trade-offs to keep implementation aligned.

The best way to align PRD, UX, and architecture documentation is running an implementation readiness check. This validates that planning artifacts and epic lists stay synchronized, preventing gaps between technical design and product goals.

Documenting technical architecture decisions for API design uses a guided workflow to record choices and constraints. This ensures the selected scalable infrastructure and API patterns stay on track during implementation.

Yes, you can use it for scalability tradeoffs and distributed systems planning. It provides persona-driven system design leadership to evaluate trade-offs, select infrastructure, and convert constraints into shippable architecture decisions.

You need to check implementation readiness for epics and stories when coordinating PRD and architecture alignment. This ensures all planning artifacts are synchronized before development begins, reducing integration risks.

System architecture planning can load contextual project details via a project-context.md file when available. This provides the necessary constraints and goals to generate accurate, shippable architecture decisions.