write-adr — Precipitate a decision into an ADR

Overview

An ADR captures one architecturally significant decision: the context that forced it, the decision taken, and the consequences accepted. The code records what was built; the ADR records why — the one thing the code can never recover. This skill runs right after concepts have been worked out: it interrogates the user until the decision is sharp, then writes it down.

Core principle: the ADR is the precipitate, not the discussion. Never transcribe the chat, and never write rationale the user does not actually hold — a guessed "why" is worse than none, because future readers will trust it.

Step 1 — Find the house rules

Discover how this repo already does ADRs before writing anything: