What problem does it solve? Verifying that a finished ticket actually passes the project's quality gates is easy to shortcut when the coordinator runs checks inline and informally. This Skill turns gate verification into a strict, checked-in, auditable procedure executed by a dedicated sub-agent, so every verdict follows the same rules defined in CLAUDE.md. ## Core Features & Use Cases - Real gate execution: Runs the exact CLAUDE.md §5 commands (typecheck, lint, test:coverage, e2e) from the ticket's worktree and records pass/fail per gate. - Acceptance-criteria verification: Maps every User Story bullet to a named test file and test case per CLAUDE.md §9, failing any criterion without located test evidence. - Ticket lifecycle integration: Transitions the ticket to verifying via spile-ops, appends a dated Notes entry with the verdict, and commits only the ticket update. - Use Case: An implementer reports ticket DH-0113 as done. You fill the prompt template with the worktree path and ticket ID, dispatch it via forked-subagent, and receive a strict PASS/FAIL report with per-gate results and coverage evidence. ## Quick Start Fill the GATE-CHECK-PROMPT.md template with the worktree path and ticket ID, then dispatch it to a sub-agent using the forked-subagent script pointed at the ticket's existing worktree.
