bmad-architecture

Invoke the skill with your SPEC.md package or PRD as input and choose the Coaching path to elicit decisions interactively, or the Fast path for a quick draft with [ASSUMPTION] tags. The output is an ARCHITECTURE-SPINE.md distilled from an append-only memlog.

A spine fixes only the invariants that prevent independently built units from diverging: paradigm, boundaries, state mutation, and data ownership. Structural details like stack and source tree are treated as seed that the code owns once it exists, keeping the document lean.

Yes. For brownfield projects the skill reads the real code and project-context.md to ratify existing conventions rather than inventing new ones. It derives the spine from what the code already shows instead of re-documenting it.

The gate runs lint_spine.py for mechanical checks like duplicate AD IDs, missing Binds/Prevents/Rule fields, and unpinned stack versions, then dispatches parallel reviewer subagents against a good-spine checklist. Under the Validate intent it delivers an HTML report without changing the spine.

Yes. Updates resume from the run's .memlog.md, amend Rules in place, and append new AD-n entries while keeping existing IDs stable. Retired IDs are never reused, so downstream specs and stories can safely cite them.

If the real need is requirements, UX design, a capability contract, or epic breakdown, the skill redirects to bmad-prd, bmad-ux, bmad-spec, or bmad-create-epics-and-stories instead. It focuses solely on architecture invariants and solution design.