game-verifylisted

# Verify ## Overview This is **PHASE 3** of the gamedev workflow: plan -> define -> build -> **verify** -> refactor The verify phase handles human playtest verification of implemented game features through structured feedback, intelligent issue categorization, and iterative fix loops until all items pass. **Trigger**: `/game-verify` or `/game-verify {feature-name}` or `/game-verify {feature-name} {feedback}` ## When to Use This skill activates in these scenarios: **Primary use:** - After `/game-build` completes implementation - When `.project/features/{name}/feature.json` exists with `tests.checklist[]` - When human verification is needed for game mechanics **Context indicators:** - Feature has been implemented with build phase - Playtest checklist exists in feature.json `tests.checklist[]` - User wants to verify gameplay feels correct **NOT for:** - Initial feature planning (use /game-define) - Implementation (use /game-build) - Automated unit testing (use /dev-verify) ## Input Formats ### Format 1: Inline feedback (recommended) ``` /game-verify water-ability 1:PASS 2:PASS 3:FAIL puddle too small 4:FAIL no sound ``` ### Format 2: Feature name only (shows checklist first) ``` /game-verify water-ability ``` ### Format 3: Free text feedback ``` /game-verify water-ability Everything works except puddle is too small and there's no sound ``` > Code quality rules: `../shared/CODING-RULES.md` (R009, TST001–TST203). TST-rules apply to GDScript/GUT test code (mock