story-done

Validate story completion against acceptance criteria and document GDD/ADR deviations.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill story-done-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/story-done
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill story-done-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill closes the loop between design and implementation by ensuring every acceptance criterion is verified, GDD and ADR deviations are surfaced, and the story status is accurately updated to Complete while surfacing the next ready story.

Core Features & Use Cases

  • Verifies acceptance criteria against the implemented story
  • Detects and surfaces GDD/ADR deviations for explicit documentation
  • Prompts for code reviews and surfaces the next ready story from the sprint

Quick Start

Run story-done with the path to the completed story to verify criteria, document deviations, prompt reviews, and surface the next ready story.

Frequently Asked Questions about story-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify acceptance criteria before marking a sprint story as Complete?

To verify acceptance criteria for sprint stories, you need a process that checks implementation against defined requirements, surfaces GDD and ADR deviations, and prompts code reviews before updating the story status to Complete.

What is the best way to document GDD and ADR deviations during story completion?

Documenting GDD and ADR deviations during story completion involves detecting discrepancies between the implemented code and the original design documents, then explicitly recording those deviations to close the loop between design and implementation.

How do I automate Definition of Done checks for sprint workflows?

Automating Definition of Done checks requires reading story metadata and ADR/GDD references to validate end-to-end completion, running DoD gates, and generating a completion report while interacting directly with story files.

Does this story completion workflow work with sprint management processes that require QA readiness?

Yes, this story completion workflow applies to sprint management processes requiring QA readiness by validating acceptance criteria, documenting design deviations, and ensuring code reviews are prompted before a story progresses to Complete.

Can I surface the next ready story automatically after completing the current one?

Yes, you can surface the next ready story automatically after completing the current one by running a validation process that updates story status to Complete and identifies the next actionable sprint item.