What problem does it solve? Teams often merge pull requests without rigorously proving the code actually satisfies the linked issue, specification, or decision record. This Skill turns an authoritative requirement into an acceptance contract and produces a criterion-by-criterion verdict instead of a vague approval. ## Core Features & Use Cases - Contract Construction: Maps every normative statement from an issue, spec, or decision record into independently decidable criteria, recording ambiguities and exclusions. - Evidence-Based Proof: Traces production code paths, runs targeted checks, and separates implementation evidence, verification evidence, and mere claims. - Structured Verdicts: Classifies each criterion as Covered, Partial, Missing, Regressed, or Unverified, then issues an overall Satisfies, Does not satisfy, or Indeterminate verdict. - Use Case: Before merging a feature branch, run the review against the linked issue to get a table showing exactly which requirements are proven, which are partial, and what evidence would close each gap. ## Quick Start Use the acceptance-review skill to decide whether this branch fulfills the linked issue with a criterion-by-criterion proof.
