← ClaudeAtlas

adr-acceptlisted

Ratify a proposed Architecture Decision Record — flip it to accepted with a date stamp, through the adr tool's fail-closed readiness gate (no placeholders, required sections present, cross-references resolve). Human-run by design; the model never invokes this on its own.
real-case/marvin-toolkit · ★ 0 · AI & Automation · score 71
Install: claude install-skill real-case/marvin-toolkit
# ADR Accept Ratify **one `proposed` record**: `proposed → accepted`, stamped with today's date. This is the human gate of the ADR lifecycle (ADR-0027) — the user runs this command deliberately; nothing else flips a record to `accepted`. The mechanics live in the **`adr` MCP tool**: its `accept` action runs a readiness gate **fail-closed** and writes nothing on refusal. This skill's job is to identify the right record, invoke the action, and turn a refusal into a fix path. ## Input `$ARGUMENTS` — the record to ratify: a number (`31`, `0031`) or a title fragment. ## Workflow ### 1. Identify the record - Call the `adr` MCP tool with `{"action": "list"}`. - Resolve `$ARGUMENTS` against the corpus (number first, then title). With no argument, show the `proposed` records and ask which one to ratify; with none, say so and stop. - Confirm the pick with the user when it came from a fragment — ratification must never land on the wrong record. ### 2. Ratify Call the `adr` MCP tool with `{"action": "accept", "number": <n>}`. On success the tool stamps status **and** date in the record's own header style and reports both. If it notes the corpus index is now stale, call `{"action": "index"}` to refresh it. Report the result: record, new status, date, path. ### 3. If the gate refuses — explain and route, never bypass The tool reports **all** gate failures at once. Translate each into its fix: | Refusal | Meaning | Fix | |---------|---------|-----| | template placeholder(s)