Review Ticket

Ticket validation against project specs requires running a comprehensive audit of deliverable file paths, acceptance criteria, SDK versions, and architecture conformity. This process enforces branch naming alignment and halts execution if the mandatory configuration file is missing.

A pre-implementation ticket audit runs a 24-check validation process covering scope gaps, deliverable file path verification, acceptance criteria checks, grep-based pattern searches, and dependency quality issues to ensure tickets align with CI process requirements.

Yes, the mandatory presence of .claude/skill-config.md is required to gate ticket review workflows. The process enforces this configuration file and halts the run if the file is missing before auditing branch naming and dependencies.

Ticket review workflows support both audit-only and audit-and-fix modes. When running in audit-and-fix mode, the process derives or checks the expected branch name, stashes work in progress, and ensures the developer is on the correct branch before changes.

Triage incoming issues during sprint planning by applying an automated ticket review that validates issue descriptions, deliverables, branch naming, and dependencies against project specifications to catch scope gaps before development begins.

Issue audits require access to issue API methods to fetch and update ticket descriptions and comments. Additionally, the process needs access to the repository source tree and git state to validate implementation tickets against project specs.