adrlisted

# ADR Skill Author or review Architecture Decision Records. An ADR captures one architectural decision: the forces at play, the choice made, the alternatives genuinely weighed, and the consequences — including the negative ones. A good ADR is honest about what becomes harder. This skill runs in one of two modes. Determine the mode first, then follow the matching steps. ## Step 1: Determine Mode - **author** — the input is a decision brief, a question, or a description of a choice to record. Produce a new numbered ADR file. - **review** — the input is a path to an existing ADR file or a directory of ADRs. Rate quality and emit a report. If the argument names a mode, use it. Otherwise infer: a path to an existing `.md` ADR ⇒ review; a decision description ⇒ author. If genuinely ambiguous, use AskUserQuestion. ## Step 2: Locate the ADR Directory Glob for an existing ADR home, in priority order: `**/docs/adr/`, `**/doc/adr/`, `**/adr/`, `**/decisions/`, `**/docs/decisions/` - **review mode** — if the input is a single file, use it directly. If it is a directory, collect every `*.md` ADR inside (skip `README.md` and `template.md`). - **author mode** — if a directory exists, compute the next sequence number from the highest `NNNN-*.md` prefix already present (e.g. existing `0007-…` ⇒ next is `0008`). If no ADR directory exists, create `docs/adr/` and start at `0001`. Use 4-digit zero-padded numbers. If multiple candidate directories exist, use AskUserQuestion to