adr-reviewlisted
Install: claude install-skill real-case/marvin-toolkit
# ADR Review
Deep review of **one `proposed` record**: validate its shape, ground its claims in the actual
codebase, fix formal defects, and deliver a verdict. The review ends in exactly one of:
- **`READY_FOR_ACCEPTANCE`** — the record is substantively sound and will pass the accept gate, or
- a **numbered defect list** — what is wrong, where, and how to fix it.
Two hard rules:
- **Never set `accepted`.** Ratification is a human decision made through `/marvin:adr-accept`
(which runs the deterministic readiness gate). This review never touches the Status field.
- **Never rewrite the substance of the decision.** The decision, its rationale, the alternatives,
and the consequences belong to the author. Weaknesses there become defects in the list, not edits.
## Input
`$ARGUMENTS` — the record to review: a number (`31`, `0031`) or a title fragment.
## Workflow
### Phase 1 — Locate the record
1. Call the `adr` MCP tool with `{"action": "list"}` and resolve `$ARGUMENTS` against it
(number match first, then title match).
2. No argument: list the `proposed` records and ask which one to review. Exactly one
`proposed` record → offer it.
3. Status check: this review targets `proposed` records. For an `accepted` / `superseded` /
`deprecated` / `rejected` record, say so and stop — reviewing a ratified record means
proposing a new one (`/marvin:adr` or `/marvin:adr-supersede`), not editing history.
### Phase 2 — Structural validation
Read the record and check its