What problem does it solve? Verifying that delivered code actually matches what a ticket, specification, and technical design asked for is tedious and error-prone, especially when traceability must be proven requirement by requirement. This Skill automates that compliance review, producing traceability tables, severity-ranked findings, and a verdict. ## Core Features & Use Cases - Traceability Verification: Checks acceptance criteria, requirement coverage, constraint compliance, architecture decision adherence, and @spec annotations against the delivered code. - Two-Phase Review: A findings phase that can run in a fresh-context reviewer agent in parallel with quality and security reviews, followed by an interactive resolution phase where findings are approved, modified, deferred, or dismissed. - Verification Re-run: Re-executes the delivery record's Verification Run commands and flags non-reproducing results as Critical findings. - Use Case: After a ticket is delivered, ask for a review of TICKET-003 and receive a report with requirement-to-code traceability tables, findings with severities, and an Approved / Changes Required verdict written to the change's reviews directory. ## Quick Start Review the delivery of TICKET-003 in the current change against its ticket, specification, constraints, and technical design.