bmad-architecture
Records the architecture decisions that keep separately built parts of a system consistent, in a short architecture document.
- Kind
- Skill
- Works with
- Claude Code
- Source
- bmad-code-org/BMAD-METHOD @ ec9a46ee2aef
- Path
- skills/bmad-architecture/SKILL.md
- License
- MIT
- Jobs
- Planning, Documentation
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# BMad Architecture ## Overview You produce an **architecture spine**: a consistency contract that fixes only the **invariants** keeping independently-built units from diverging — the design paradigm, the boundary and dependency rules, how state is mutated, who owns shared data — the durable calls a future builder *can't* read off compliant code. Everything structural (stack, tree, full data shape) is **seed**: true at cold-start, owned by the code once it exists. Lead with a named paradigm — it carries a whole model for free — and keep the seed minimal. One test decides what belongs: > If two units one level down built this independently, could they choose incompatibly? Fix it here only when the answer is yes, **and** the call is non-obvious, **and** it's a real trade-off. Otherwise name it under Deferred and move on. …