bmad-create-architecture

Define architectural decisions with rationale and requirement mappings.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-create-architecture-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-create-architecture
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-create-architecture-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create architecture decisions and collaborative workflows to ensure AI agents implement projects consistently.

Core Features & Use Cases

  • Facilitates parallel architecture decision-making across teams
  • Guides AI agents through stepwise architecture lifecycle with versioned rationales
  • Provides traceable decisions and commitments to ensure consistent implementation

Quick Start

Provide a project context and guide the architecture workflow, then respond to prompts to steer AI agents through decision steps.

Frequently Asked Questions about bmad-create-architecture

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

FAQPage Schema
How do I define architecture decisions for consistent AI agent implementation?

To define architecture decisions for consistent AI agent implementation, establish explicit mappings from requirements to architecture, including patterns, structure, and boundaries. This provides traceable decisions and commitments to ensure deterministic implementation across future projects.

How does architecture decision mapping work for AI workflows?

Architecture decision mapping for AI workflows works by guiding AI agents through a stepwise architecture lifecycle with versioned rationales. This provides explicit mappings from requirements to architecture, ensuring traceable decisions and commitments for consistent implementation.

How to guide AI agents through stepwise architecture lifecycle decisions?

To guide AI agents through stepwise architecture lifecycle decisions, provide a project context and steer the architecture workflow by responding to prompts. This facilitates parallel decision-making across teams while maintaining versioned rationales and traceable commitments.

Can I use this architecture workflow for parallel team collaboration?

Yes, you can use this architecture workflow for parallel team collaboration. It facilitates parallel architecture decision-making across teams by providing traceable decisions and commitments that ensure consistent implementation by AI agents throughout the project lifecycle.

Why does AI agent implementation lack consistency without architecture decisions?

AI agent implementation lacks consistency without architecture decisions because there are no explicit mappings from requirements to structure, patterns, and boundaries. Without versioned rationales and traceable commitments, agents cannot achieve deterministic implementation across future projects.

What are the limitations of relying on AI agents without traceable architecture decisions?

Relying on AI agents without traceable architecture decisions limits implementation consistency and deterministic outcomes. Without explicit requirement mappings, versioned rationales, and documented compatibility, agents cannot maintain traceable commitments across future projects and teams.