implement-validate

Validating Jira ticket readiness involves checking the target repository, acceptance criteria, and DoD references to decide if the ticket can enter the build pipeline. The skill automates this by scoring readiness and posting a phase marker to Jira.

Automating sprint ticket gating requires scoring each ticket against ADR mappings and acceptance criteria. This skill computes a 0–10 readiness score and transitions the ticket status to pass, out-of-scope, rejected, or critical-park accordingly.

Automated ticket validation handles missing acceptance criteria by rejecting the ticket with a needs-info status. The skill posts actionable feedback as a phase marker to Jira, detailing inferences and required updates before the build can proceed.

You can use Jira labels and component fields to verify correct repository targeting. The skill inspects these fields alongside ADR mappings to ensure the sprint ticket aligns with the current repo before passing it to the build pipeline.

A Jira ticket receives a critical-park status during readiness validation when critical requirements or ADR mappings are missing. The skill assigns this outcome to block the ticket from entering the build pipeline until the blockers are resolved.

The implement-validate skill requires no external dependencies to assess ticket readiness. You provide a Jira ticket key and resolved configuration, and it evaluates readiness against specs and DoD references without additional modules.