ADR Keeper

Architectural Decision Records capture the WHY behind structural choices. They are append-only (never edit old decisions — supersede with new ones) and sorted chronologically like database migrations.

When to Create an ADR

• Choosing or changing a dependency
• Establishing or changing an architectural pattern
• Making a trade-off that future developers (or agents) need to understand
• Any decision where "why did we do it this way?" would be asked later

File Location & Naming

ADRs live in docs/adrs/ (created by create-claude-md, or create manually).

Naming: YYYY-MM-DD-short-kebab-description.md