What problem does it solve? Shipping a milestone without rigorous verification leads to unchecked acceptance criteria, stale evidence, and unreviewed code reaching the default branch. This Skill enforces a gated review workflow in cairn-tracked repositories so every milestone is verified against fresh evidence before merge. ## Core Features & Use Cases - Evidence-based verification: Re-runs every acceptance criterion and records fresh evidence in the milestone's Review section before ticking any checkbox. - Consistency gate and independent review: Runs mechanical cairn-file validation plus toolchain checks, then spawns fresh-context reviewers (diff-bug, blame-history, prior-PR-comments lenses) scaled to the milestone's surface tier. - Approval-gated merge: Presents findings for triage, obtains explicit user approval via a chip, then pushes, opens the PR, waits for green CI, and squash-merges with a merge-approval marker. - Use Case: After implementing milestone M42 in a cairn repo, run the review to verify all criteria, get an independent three-lens code review, and merge the PR only after your explicit approval. ## Quick Start Ask the assistant to review and ship milestone M42 by running /milestone-review M42 in a cairn-tracked repository.