adr

# ADR Skill Capture architectural decisions as they happen, so the *why* lives next to the code instead of in a Slack thread or someone's memory. Produces lightweight ADR documents under `docs/adr/`. ## Keywords adr, architecture decision record, decision, rationale, trade-off, alternatives, we decided, why did we choose, design decision, supersede, decision log, nygard ## When to record a decision - The user says "record this", "ADR this", "let's document this decision". - A choice is made between **significant alternatives**: framework, library, database, language, pattern, API shape, infra/deploy approach, build vs buy. - The user says "we decided to…" or "the reason we're doing X instead of Y is…". - The user asks "why did we choose X?" → read and summarize the existing ADR. For trivial or easily-reversible choices, don't create an ADR — note it inline and move on. ## Output Artifacts | Request | Output | |---------|--------| | `/adr new "<title>"` | A new `docs/adr/NNNN-<slug>.md` + an updated index | | `/adr list` | The decision log (ID, title, status, date) | | `/adr supersede <NNNN>` | A new ADR marked as superseding an old one; old one flipped to `superseded` | --- ## Format Lightweight Nygard ADR, adapted for AI-assisted work: ```markdown # ADR-NNNN: <Decision Title> **Date**: YYYY-MM-DD **Status**: proposed | accepted | deprecated | superseded by ADR-NNNN **Deciders**: <who was involved> ## Context What is the issue motivating this decision? The sit...