bmad-create-architecture

Creates architecture decision artifacts from enterprise requirements for agent-driven implementation.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-architecture-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/3-solutioning/bmad-create-architecture
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-architecture-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts early product intent into a complete set of architecture decision artifacts so multiple AI agents implement consistently, without drifting into conflicting design choices.

Core Features & Use Cases

  • Collaborative architecture facilitation: Guides you step-by-step through architecture setup, requirement analysis, decision capture, and validation.
  • Workflow-driven consistency: Uses a micro-file step process and documented patterns to prevent agents from making incompatible changes.
  • Configurable, source-aware initialization: Loads project context and facts from discovered files, then structures the resulting architecture workspace.

Quick Start

Activate the bmad-create-architecture skill and say: "Let's create a solution design and architecture for our project."

Frequently Asked Questions about bmad-create-architecture

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

FAQPage Schema
How do I create consistent architecture decisions from enterprise requirements?

To create consistent architecture decisions, you need a workflow orchestration process that analyzes project context, documents decisions, and enforces consistency rules to prevent multiple AI agents from drifting into conflicting design choices.

What is the best way to prevent AI agents from making incompatible architecture changes?

The best way to prevent incompatible architecture changes is using a micro-file step process with documented patterns that enforce consistency rules, ensuring all agents reference the same validated architecture decisions during implementation.

How does workflow-driven solution design handle project context analysis?

Workflow-driven solution design analyzes project context by loading persistent facts from discovered files, merging workflow customization, and structuring the resulting architecture workspace for guided step progression and agent collaboration.

Can I use this architecture discovery workflow for multi-agent implementation projects?

Yes, this architecture discovery workflow is specifically built for agent-driven implementation, producing decision records and validation readiness checks that ensure multiple agents implement consistently without conflicting design choices.

Do I need existing project files to start capturing architecture decisions?

Capturing architecture decisions benefits from existing project files but does not strictly require them; the workflow loads persistent facts from discovered files to initialize context, then guides step-by-step decision documentation with user-controlled progression.