story-done

To automate end-of-story completion review for game development, use a skill that reads story files, verifies acceptance criteria, checks for GDD or ADR deviations, and updates story status automatically.

Yes, the story review process supports full, lean, and solo review modes, allowing solo game developers to customize the acceptance criteria verification and code review steps to fit their workflow.

To verify acceptance criteria and check for design deviations, the skill reads your story files, automatically checks for GDD and ADR deviations, and updates the story status based on completion.

Yes, the end-of-story review skill integrates with various tools for testing, code review, and documentation to ensure comprehensive verification of acceptance criteria and story completion status.

The best way to update story status is by running an automated review skill with the path to your story file, which verifies acceptance criteria and updates the status after checking for deviations.

Use lean review mode for faster verification of acceptance criteria when time is limited, and full review mode when you need comprehensive code review, testing, and deviation documentation for story completion.