bmad-agent-architect

Convert product requirements and UX into technical architecture within the BMAD Method workflow.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-agent-architect-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-architect
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-agent-architect
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-agent-architect-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps translate product requirements and UX into clear technical architecture decisions that keep implementation aligned during the BMAD workflow.

Core Features & Use Cases

  • Technical architecture leadership: Produces system design guidance when users ask for the architect or reference Winston.
  • BMAD-ready activation flow: Resolves agent configuration, runs activation steps, loads persistent facts, and ingests project config for consistent outputs.
  • Menu-driven dispatch: Offers architecture and implementation-readiness actions, such as documenting architecture decisions and aligning PRD/UX/epics/stories.

Quick Start

Ask Winston to architect your system and align the PRD, UX, and implementation plan using the BMAD workflow.

Frequently Asked Questions about bmad-agent-architect

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

FAQPage Schema
How do I turn product requirements into shippable system architecture?

To turn product requirements into shippable system architecture, this skill applies the BMAD workflow to translate your PRD and UX designs into clear technical architecture decisions. It ensures implementation readiness by aligning planning artifacts with system design.

What is the BMAD methodology for technical design?

The BMAD methodology for technical design is a workflow that converts product requirements and UX into technical architecture. It uses an agent orchestration persona to align the PRD, UX, epics, and stories for implementation readiness.

How do I align PRD, UX, and implementation plans using agent orchestration?

You align PRD, UX, and implementation plans by dispatching the system architect agent to resolve customization configurations and execute readiness actions. This ingests project TOML files and persistent facts to ensure all planning artifacts match.

Do I need a PRD before starting system architecture design?

Yes, a PRD is needed before starting system architecture design because the skill converts existing product requirements and UX into technical decisions. Without these inputs, the architecture cannot align with implementation readiness.

Can I use project TOML files to customize agent orchestration for requirements to engineering?

Yes, you can use project TOML files to customize agent orchestration for requirements to engineering. The skill executes customization resolution from both skill and project TOML files, loading persistent facts and BMAD config for consistent outputs.

What are the limitations of automating requirements to engineering conversion?

A limitation of automating requirements to engineering conversion is that it strictly operates within the BMAD Method workflow. Architecture decisions depend entirely on the completeness of your PRD, UX, and planning artifacts provided to the agent.