epic-verify-ticket

Ticket verification against requirements is performed by analyzing git diff, checking the completion report, and validating acceptance criteria to ensure changes align with the ticket specification. It generates a PASS, FAIL, or NEEDS_FIXES verification report.

Ticket verification is the process of validating code changes against ticket specifications and acceptance criteria to detect regressions. You need it after ticket execution to ensure implementation meets requirements and passes quality assurance gates before a manifest update.

Checking acceptance criteria and detecting regressions in a git diff involves comparing ticket specifications against code changes using jCodemunch analysis. It identifies unintended side effects, logic drift, and verifies each criterion against the completion report.

Yes, you need Python and jCodemunch to generate a verification report because Python scripts handle manifest manipulation while jCodemunch performs code analysis. Git is also required as a dependency to analyze the ticket diff.

Yes, you can use this skill to update a manifest with verification status and notes. After validating ticket implementation and generating a verification report with a verdict, it automatically updates the execution manifest.

The best way to validate manifest completion for a ticket specification is to run a verification skill that checks the execution phase, analyzes the git diff with jCodemunch, and verifies acceptance criteria to ensure all gates pass before updating the manifest.