write-adrlisted

# /write-adr Draft an Architecture Decision Record for: `$ARGUMENTS` Project-agnostic: the repo's **existing ADRs are the format spec**. This skill discovers them rather than imposing a house style, so a repo that says `## Trade-offs` where another says `## Consequences` keeps its own convention with no configuration. **Scope: new ADRs only.** Amending an existing ADR is ordinary editing — the numbering, template discovery, and review loop here all assume a file that does not exist yet. If the user wants a change to an already-written ADR, edit it directly instead of invoking this. A project with its own `write-adr` skill shadows this one (project scope wins) — expected, and there is no obligation to keep the two in sync. ## Step 1 — Discover 1. **ADR directory**: glob for a directory containing `ADR-*.md` / `adr-*.md` — try `docs/decisions/`, `docs/adr/`, `doc/adr/`, `docs/architecture/decisions/`. A bare `NNN-*.md` naming also counts, but only if the directory *also* looks like a decision log (an `INDEX.md` of decisions, or files whose headings read as decisions) — a numeric-prefix glob alone matches ordinary numbered docs (`001-getting-started.md`) and would drop an ADR into an unrelated series. If several directories match, ask. **If none exists**, ask the user where to write and use the skeleton in Step 2. 2. **The numbering scheme, then the main sequence.** First decide what the numbers *are*: a flat monotonic counter (`ADR-007`), or date/year