create-adrlisted

# Create ADR Record one architecture decision — the "why" that code and commit messages can't carry — as a numbered, immutable file in the target repository. An ADR records a **decision made**, not a proposal under discussion. If the decision isn't settled yet, help settle it in conversation first; write the ADR after. ## Steps 1. **Locate the ADR home.** Look for an existing convention in the target repo: `docs/adr/`, `docs/decisions/`, `adr/`, or an existing `NNNN-*.md` series anywhere under `docs/`. Follow whatever exists (numbering width, template style). If none exists, create `docs/adr/` and start at `0001`. - Completion criterion: directory and next sequence number are known. 2. **Gather the decision.** From the conversation (ask only for gaps): the decision itself, the context/forces that made it necessary, the alternatives considered, and why they lost. If the decision came out of work in this session, pull the concrete evidence (files, constraints) you already have instead of re-asking. 3. **Draft the ADR** — in English, as a repository artifact. Template (skip a section only when genuinely empty, and keep the heading with "None."): ```markdown # NNNN. <Decision title, imperative — "Use X for Y"> Date: YYYY-MM-DD Status: Accepted ## Context <the forces: requirements, constraints, problems that made a decision necessary> ## Decision <what was decided, stated as fact> ## Alternatives considered <ea