create-adrlisted

# Create ADR ## Overview ADRs capture significant architectural decisions with enough context for a future session to understand the *why*, the alternatives, and the consequences. The value this skill adds over free-hand note-taking is the **conflict gate**: every new ADR is reviewed against all existing ADRs for the same repo, and **no decision may silently contradict an accepted one** — it must either supersede it or justify coexistence. This brain already has an ADR convention (see `memory/repo/ui/adr/`, `memory/repo/streaming/adr/`). Match it — do **not** invent a heavier template. ## Context Before starting, read the repo's `CLAUDE.md` / `CLAUDE.local.md` and the relevant `memory/repo/<repo>/` notes for prior decisions and constraints. ## Step 1 — Locate the ADR directory Decide where the ADR lives: - **Target project has its own `docs/adr/`** (or `docs/decisions/`) → write there, in that project's format. - **Otherwise (default for this brain)** → `memory/repo/<repo>/adr/`, using this brain's format below. `<repo>` is the short repo name already used under `memory/repo/`. ```bash ls docs/adr docs/decisions 2>/dev/null # target-project convention? ls memory/repo/<repo>/adr 2>/dev/null # brain convention (default) ``` ## Step 2 — Review existing ADRs before writing (MANDATORY) Read **every** ADR already in the chosen directory. Do not skip this — it's the whole point of the skill. ```bash ls memory/repo/<repo>/adr/ | sort ``` For each e