story-done

To verify game development stories, you can cross-reference acceptance criteria with implementation files and design documentation. This skill executes automated checks for test coverage, GDD alignment, and architectural constraints before marking stories complete.

Automated QA sign-off is facilitated by coordinating with the QA lead to ensure logic, integration, and visual or feel criteria are met. Verification gates check file existence, test coverage, and GDD adherence across the project lifecycle.

A verification gate is an automated checkpoint that validates story completion by checking file existence, test coverage, and adherence to GDD requirements. It ensures development stories are verified against design documents and architectural constraints before completion.

Sprint status updates automatically when verification passes. The system surfaces the next ready story and transitions the current story through development, QA sign-off, and sprint progression using structured verification gates.

Story verification operates with no external dependencies. It cross-references acceptance criteria with implementation files and design documentation internally to execute automated checks for test coverage and architectural constraints.