bmad-create-architecture

Guide stepwise collaborative workflows to create architecture decisions for AI agents.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-create-architecture-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-create-architecture
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-create-architecture-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a collaborative, stepwise process to produce architecture decisions for AI agents that are consistent across implementations.

Core Features & Use Cases

  • Workflow-driven architecture leadership with frontmatter-driven state tracking and step-by-step guidance.
  • Collaborative elicitation, decision making, and pattern establishment to ensure uniform implementation across agents.
  • Use Case: A team wants to align multiple AI agents on the same architectural decisions for a complex project.

Quick Start

Initiate the architecture workflow for the current project and guide me through step-by-step, collaborative decisions.

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 architecture decisions that ensure AI agents implement consistently?

To create architecture decisions for AI agents, use a collaborative, stepwise workflow that guides elicitation and pattern establishment. This approach tracks progress using YAML frontmatter to ensure uniform implementation across multiple agents.

What is the best way to align multiple AI agents on the same architectural decisions?

The best way to align multiple AI agents is through workflow-driven architecture leadership that uses collaborative elicitation and decision making. This establishes uniform patterns and tracks step-by-step progress to maintain consistency across implementations.

How does frontmatter-driven state tracking work for step-by-step architecture workflows?

Frontmatter-driven state tracking uses a unique identifier in YAML frontmatter to monitor progress across pre-defined steps. This mechanism ensures safe step execution and maintains state throughout the collaborative architecture decision process.

Can I include external resources and scripts in my architecture decision workflow?

Yes, you can include optional resources under scripts, references, and assets directories within your architecture decision workflow. These components support the stepwise process while maintaining safe step execution and frontmatter-tracked progress.

Do I need YAML frontmatter to track progress in a collaborative architecture workflow?

Yes, YAML frontmatter with a unique identifier is required to track progress accurately in the architecture workflow. This ensures safe step execution and maintains state across collaborative elicitation and decision-making steps.

When should I use a stepwise workflow for architecture decisions instead of ad-hoc documentation?

Use a stepwise workflow when a team needs to align multiple AI agents on complex architectural decisions. The structured process with collaborative prompts and frontmatter-tracked state ensures consistent implementation across all agents.