adrlisted
Install: claude install-skill real-case/marvin-toolkit
Draft an Architecture Decision Record (ADR) documenting a significant technical decision.
The deterministic mechanics — next number, target path, corpus discovery, index regeneration —
belong to the **`adr` MCP tool** (from the `marvin` server, ADR-0027). This skill owns only the
judgement work: gathering context, weighing alternatives, and writing the prose. Never hand-number
a record or hand-maintain the index.
A draft **always lands with status `proposed`** — never `accepted`. Authority lives at the gates:
ratification is `/marvin:adr-accept`, rollback is `/marvin:adr-supersede`, both human-run.
## Argument handling
- `/marvin:adr <title>` — use the provided title as the decision topic
- `/marvin:adr <title> --context <path>` — use research notes from the given file as additional input
- `/marvin:adr` — ask the user what decision they want to document
## Phase 1: Discover the corpus and project conventions
1. Call the `adr` MCP tool with `{"action": "list"}` — it resolves the corpus location
(config `adr.dir` → detected `docs/adr/` / `docs/decisions/` / `adr/` → default `docs/adr/`)
and returns every existing record with number, title, and status. Note records related to
this decision, and any malformed files it reports.
2. If records exist, read 2–3 recent ones to match the corpus's **style, tone, and header
format** — marvin-style table headers (`| Status | … |`) and MADR-style sections
(`## Status`) both parse; new records should match their neighbo