Free kit · MIT license
The Decision Register is a one-page interactive template for working through many decisions at once: audit findings, rules to reconcile, proposals, backlog or risk triage. Each item becomes a card with the context, the reference it is judged against, a recommendation and Keep / Remove / Discuss buttons. Your choices are saved and can be exported.
In plain English, with evidence: who or what is affected, when, and how often. Plus where it lives and where it came from.
A short quote from the policy, handbook or spec that governs it, or a plain note that the reference is silent.
Keep / Remove / Discuss by default, or any choices you configure. "Use my recommendation" fills it in; a note field captures the why.
Unzip, then copy the folder into your skills directory:
cp -R decision-register-kit \ ~/.claude/skills/decision-register
Then ask for it: "Audit our deploy scripts against the release policy and give me the results as a decision register."
Copy and edit the two example JSON files, then build:
python3 scripts/build.py \ --config my-config.json \ --items my-items.json --out out
Open out/register.html or send it to whoever decides.
register.html is a single static file, so any static host works. Each visitor's decisions stay in their own browser; they export them with "Download decisions (JSON)" or "Copy my decisions as text".
The format was devised with Claude in Claude Code in October 2026, during an audit of rules that software agents had been following although nobody had approved them. That review produced 140 decisions, and the format was worth keeping for the next batch.
It borrows from familiar practices: decision logs and architecture decision records, review checklists, triage boards and "accept the recommendation" workflows. The full field reference is in the README.