bmad-agent-architect

Guide technical design decisions for scalable backend and API architectures.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-agent-architect-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-architect
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/bmm/3-solutioning/bmad-agent-architect
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-agent-architect-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users through technical design decisions by embodying Winston, a senior system architect, to help plan scalable architectures and make pragmatic trade-offs.

Core Features & Use Cases

  • Provides architecture guidance during design reviews, technology selection, and system decomposition for scalable distributed systems.
  • Facilitates alignment between product goals, engineering constraints, and deployment realities through structured decision workflows.
  • Use Case: When evaluating a new service, Winston outlines architectural trade-offs between monoliths and microservices, data partitioning, and deployment strategies.

Quick Start

Start by describing your system's goals and constraints, and ask Winston to outline a scalable architecture plan.

Frequently Asked Questions about bmad-agent-architect

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

FAQPage Schema
How do I make architecture decisions for scalable distributed systems?

Scalable distributed systems architecture decisions are guided by evaluating system goals, constraints, and trade-offs. A structured workflow aligns product requirements with engineering realities to produce pragmatic technology choices and deployment strategies.

What is the best way to choose between a monolith and microservices for my backend?

Choosing between monoliths and microservices requires evaluating architectural trade-offs like data partitioning and deployment complexity. Structured guidance outlines these differences to help you select the right system decomposition for your backend.

How do I plan API design for a new service?

API design planning for a new service involves defining technical requirements and deployment realities. Structured decision workflows guide you through technology selection and system decomposition to ensure your API meets scalability and product goals.

Can I get architecture review guidance for cloud scalability?

Yes, architecture review guidance for cloud scalability is provided by analyzing technical design decisions. It helps evaluate technology choices and plan distributed systems by applying structured safety checks and project context alignment.

When do I need structured guidance for system decomposition?

Structured guidance for system decomposition is needed when evaluating new services and facing complex architectural trade-offs. It helps facilitate alignment between product goals, engineering constraints, and deployment realities for scalable APIs.