bmad-architecture

Creates and validates architecture spine documents recording binding system design decisions.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-architecture-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-architecture
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-architecture
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-architecture-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Teams building separate parts of a system drift into incompatible choices. This Skill produces an architecture spine — a short document fixing only the invariants (paradigm, boundaries, state mutation, data ownership) that keep independently built units consistent. ## Core Features & Use Cases - Create, update, or validate a spine: Works from a spec, a raw idea, or an existing codebase, at initiative, feature, or epic altitude, with stable AD-n decision IDs. - Coaching or Fast path: Elicits decisions through open-ended questions by default, or drafts the full spine with [ASSUMPTION] tags for review. - Reviewer Gate: Runs a deterministic lint_spine.py pass plus parallel reviewer subagents against a good-spine checklist before handoff. - Use Case: Point it at a brownfield codebase to ratify existing conventions into an ARCHITECTURE-SPINE.md with a memlog of every decision, then validate it before handing off to story-level work. ## Quick Start Ask the assistant to create the technical architecture for your project from your spec or existing codebase.

Frequently Asked Questions about bmad-architecture

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

FAQPage Schema
How do I create a software architecture document from a spec?▼

Invoke the skill with your spec package and it elicits the load-bearing decisions, then distills an ARCHITECTURE-SPINE.md with AD-n decision blocks, a stack table, and diagrams. Every decision is logged to a memlog as it is made.

How do I derive architecture decisions from an existing codebase?▼

Point the skill at the brownfield code and it investigates the real conventions already present, ratifying them as adopted decisions rather than inventing new ones. The resulting spine records only the invariants a future builder could not read off the code.

Can I validate an existing architecture document without changing it?▼

Yes, the Validate intent runs the Reviewer Gate against the spine: a deterministic lint_spine.py pass plus parallel reviewer subagents. It delivers a bespoke HTML report of findings and offers to roll them into an update.

What is the difference between the Coaching path and Fast path?▼

The Coaching path is the default and pulls decisions out of you through open-ended questions, pushing back on thin calls. The Fast path drafts the whole spine quickly with [ASSUMPTION] tags that you correct in review.

When should I not use an architecture spine?▼

If your real need is requirements, UX, a capability contract, or epic breakdown, the skill routes you to the appropriate PRD, UX, spec, or epics skill instead. A spine only fixes cross-unit invariants, not full system detail.