ADR Writing Weapon

Architecture Decision Records (ADRs) are the smallest useful unit of institutional memory. This Weapon encodes everything needed to author, govern, and maintain an ADR corpus: the Nygard canonical format, the MADR and Y-statement variants, the supersession lifecycle, lightweight tooling (Log4brains, adr-tools), and the "decisions, not docs" discipline that keeps ADR logs scannable and trustworthy across years of codebase evolution.

When to use this weapon

Activate when the user:

• Says "write an ADR", "record this decision", "document our architecture choice", "create an ADR for X"
• Wants to supersede an existing ADR ("we changed our minds about X", "supersede ADR-007")
• Needs to set up an ADR log from scratch ("we've never done ADRs before")
• Asks about tooling ("should we use Log4brains or adr-tools?", "how do I generate ADR HTML?")
• Wants to use ADRs for onboarding ("how do new engineers read our ADR log?")
• Asks about format choices ("Nygard vs MADR vs Y-statements?")