write-adrlisted

# write-adr - capture an architecture decision An ADR (Architecture Decision Record) is a short markdown file that explains: - The **context** that made the decision necessary. - The **decision** itself. - The **alternatives** considered and why they lost. - The **consequences** - what's better, what's worse, what's now harder. Good ADRs answer "why did we do X instead of Y?" months later, when the person who knew has left or forgotten. This skill discovers the repo's existing ADR convention, discusses the decision with the user, then writes the ADR matching the local format. ## Phase 0 - Find existing ADRs Hunt for the ADR directory and format. Don't assume; the repo tells you what to do. ```bash # Common ADR locations, in priority order. for d in docs/adr docs/architecture/decisions docs/decisions adr decisions; do if [ -d "$d" ]; then echo "$d"; fi done # Fallback: search broadly. fd --type f --extension md '^[0-9]+[-_]' . 2>/dev/null | head -20 rg -l --type md '^# *ADR' . 2>/dev/null | head -10 ``` If you find existing ADRs, **read 2-3 of them** to extract the convention: - Location and numbering scheme (e.g. `NNNN-title.md` zero-padded, or `ADR-NNN-` prefix, or unnumbered). - Format and frontmatter (see `references/adr-formats.md` for common patterns). - Typical length - match it. - `Status` transitions tracked (Proposed → Accepted → Superseded)? - Category/component tags? If **no existing ADRs** are found, default to **MADR v3.0** (the most common moder