bmad-architecture
Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a ticket file, with an existing codebase or architecture document beside it. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"
Install
git clone https://github.com/bmad-code-org/BMAD-METHOD /tmp/BMAD-METHOD && ln -s /tmp/BMAD-METHOD/skills/bmad-architecture ~/.claude/skills/bmad-architectureFrom README
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. Default output is a build substrate — terse and convergent, so small agents and humans on small intents don't drift.
More from this repo
bmad
Answers BMad questions and recommends the next skill from what is installed.
bmad-advanced-elicitation
Push the LLM to reconsider, refine, and improve its recent output.
bmad-agent-analyst
Business analyst for market research, competitive analysis, and requirements.