What problem does it solve? Closing a development story often skips verification: acceptance criteria go unchecked, GDD or ADR deviations slip in silently, code review is forgotten, and sprint status files drift out of sync. This Skill enforces a structured end-of-story review so a story is only marked Complete after evidence is confirmed. ## Core Features & Use Cases - Acceptance Criteria Verification: Automatically checks file existence, test passes, and hardcoded values, batches manual confirmations, and builds a test-criterion traceability table with COVERED/UNTESTED escalation rules. - Deviation and Evidence Gates: Compares implementation against the TR registry, control manifest version, and ADRs, enforces test evidence requirements per story type (Logic, Integration, Visual/Feel, UI, Config/Data), and runs QA coverage and lead-programmer review gates in full mode. - Status Updates and Sprint Continuity: Updates the story file to Complete, logs tech debt, refreshes sprint-status.yaml and session state, suggests a git commit, and surfaces the next ready story or the sprint close-out sequence. - Use Case: After implementing a damage calculator story in a Godot project, run the review to confirm all criteria pass, the unit test exists, no GDD deviations exist, then close the story and pick up the next ready sprint item. ## Quick Start Use the story-done skill to review and close the story at production/epics/core/story-damage-calculator.md and report the verdict.
