bmad-agent-architect

Translates product requirements and UX into technical architecture documentation and decisions.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-agent-architect-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-architect
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-agent-architect
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-agent-architect-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates product requirements and UX into robust technical architecture that guides implementation, reducing drift and rework while promoting stability and developer productivity.

Core Features & Use Cases

  • System-architecture leadership: define tech patterns, stack choices, and governance for projects.
  • Design collaboration: translate PRDs and UX into actionable architecture decisions and documentation.
  • Activation-time persona: act as Winston to steer architectural trade-offs and maintain project focus.

Quick Start

Provide a high-level architecture plan for the current project requirements to Winston.

Frequently Asked Questions about bmad-agent-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate product requirements into a robust technical architecture?

Translate product requirements into technical architecture by defining tech-stack decisions, governance, and architecture documentation to guide implementation and reduce drift. This ensures clear alignment between UX goals and engineering execution.

What is the best way to document architectural trade-offs for cross-functional teams?

Document architectural trade-offs by maintaining traceable architecture decisions and design review rigor. This enables cross-functional team alignment and provides clear rationale for tech-stack choices during system design.

How do I ensure team alignment on system design for a large-scale project?

Ensure team alignment on system design by establishing architectural leadership that defines tech patterns and governance. This guides medium- and large-scale projects, reducing rework and promoting developer productivity.

Can I use an engineering lead persona to steer system architecture decisions?

Use an engineering lead persona to steer system architecture decisions by activating a dedicated persona to maintain project focus. This persona translates requirements into actionable architecture decisions during design collaboration.

When do I need formal architecture documentation for my project?

You need formal architecture documentation for medium- and large-scale projects with cross-functional teams. It provides the necessary design review rigor and traceable trade-off documentation to prevent implementation drift.

How do I design technical architecture that actually ships and reduces rework?

Design technical architecture that ships by translating UX and product requirements into robust system patterns. This approach reduces drift and rework while promoting stability and developer productivity throughout implementation.