ratification-docketlisted
Install: claude install-skill seevali/claude-skills
# Ratification Docket
The owner should be able to rule on every open decision from one page, in plain language, without opening a single source
document. The page collects the rulings; a dated decision record is the durable result. The page is never the record.
## When this applies
A body of proposed decisions exists on disk — a decision record with `Status: Proposed` lines, a report with numbered
recommendations, a tracker with operator gates — and the owner must rule. The failure mode this skill exists to prevent: a
walkthrough that mirrors the documents' structure and vocabulary (item codes, section numbers, internal finding labels), so
that to answer one line the owner has to go and read what a "W6" or an "OPEN-5(b)" is. That violates the point of the session.
## The Protocol
### 1. Collect every proposed item, with its default
- Enumerate all of them across every document in scope: Proposed decisions, numbered recommendations, operator gates,
open questions. Record for each what it proposes, its default if unanswered, and which document owns it.
- Check ground truth that bears on the rulings before writing anything (has any of the proposed work started? are the dates
already past? does a referenced repository, package or page exist?). Rulings made on stale premises are wrong rulings.
### 2. Verify the supersession map before the owner sees it
- When two or more documents overlap, map where the later one **supersedes** (changes what the earlier decides), **ret