What problem does it solve? Teams often merge pull requests without rigorously proving the code actually satisfies the original issue, specification, or decision contract. This Skill performs a read-only audit that maps every normative requirement to a decidable criterion, traces the production code path, executes verification checks, and returns a clear acceptance verdict instead of a vague code review. ## Core Features & Use Cases - Contract Construction: Resolves the authoritative artifact (issue, spec, or accepted decision), maps each normative statement to one criterion, and records ambiguities and exclusions. - Evidence Lanes: Separates implementation evidence, executed verification, and mere claims (PR prose, commit messages) so intent is never confused with behavioral proof. - Machine-Readable Verdicts: Returns VERDICT: satisfies, VERDICT: does-not-satisfy, or VERDICT: indeterminate with a criterion-by-criterion table citing exact files and lines. - Use Case: Before merging a branch that claims to close an issue, run this Skill to confirm every acceptance criterion is covered by traced code and executed checks, and to identify exactly what evidence would close any gap. ## Quick Start Ask the agent to use acceptance-review to decide whether the current branch satisfies the linked issue, producing a criterion-by-criterion proof and verdict.
