What problem does it solve? A test file that exists and passes may still leave critical behaviour uncovered, and a manual evidence document may lack required sign-offs. This Skill audits the quality of test files and evidence documents for game production stories, assigning an ADEQUATE, INCOMPLETE, or MISSING verdict per story before QA sign-off. ## Core Features & Use Cases - Automated test quality review: Evaluates assertion coverage per test function, edge case handling, naming conventions, and formula traceability for Logic and Integration stories. - Manual evidence review: Checks criterion linkage, developer/designer/QA sign-off completeness, screenshot artefacts, and evidence freshness for Visual/Feel and UI stories. - Verdict reporting: Produces a story-by-story report with BLOCKING and ADVISORY issues, plus an overall sprint or system verdict, optionally written to production/qa/evidence-review-[date].md. - Use Case: Before closing a sprint, run the review across all stories to find a Logic story whose test passes vacuously with zero assertions and a Visual/Feel story missing the QA lead sign-off, then resolve both before story-done. ## Quick Start Ask the assistant to run a test evidence review on the current sprint and report which stories have adequate, incomplete, or missing test evidence.
