story-done

Validate story implementation against acceptance criteria and generate a completion report.

Updated Apr 24, 2026

Search Tags:#documentation #qa #sprint #acceptance-criteria #deviations #story-management

Ready to run

npx skills add https://github.com/rakhnianskii9/God-Godot --skill story-done-rakhnianskii9

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/story-done
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill story-done-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-story completion is error-prone and time-consuming; this Skill streamlines verification of criteria, documentation consistency, and final status updates to Complete while surface the next ready story.

Core Features & Use Cases

Acceptance verification: reads the story, validates each acceptance criterion against implementation, and reports deviations from GDD/ADR.
Status updates & handoffs: marks the story as Complete, surfaces the next ready sprint story, and surfaces required follow-up actions.
Audit-ready output: produces a completion report suitable for stakeholder sign-off and sprint tracking.

Quick Start

Run story-done with a path to a story file to automatically complete it.

Frequently Asked Questions about story-done

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

FAQPage Schema

How do I automate sprint story completion and acceptance criteria verification?▼

Automate sprint story completion by running the Skill with a path to a story file; it validates each acceptance criterion against implementation, captures deviations, and updates the story status to Complete.

What is the best way to document story deviations and QA gate decisions for sprint tracking?▼

Documenting story deviations and QA gate decisions involves generating an audit-ready completion report that captures test evidence and GDD/ADR references, ensuring stakeholders have a reliable record for sign-off.

How does acceptance verification work for completed development stories?▼

Acceptance verification reads the story file, checks each defined criterion against the actual implementation, and surfaces any deviations from the referenced GDD or ADR documentation for review.

Can I use this workflow for sprint stories without defined acceptance criteria?▼

This workflow is designed for sprint stories with defined acceptance criteria; stories lacking these criteria or GDD/ADR references cannot be properly validated for deviations and completion.

How do I surface the next ready sprint story after marking the current one complete?▼

Surfacing the next ready sprint story happens automatically during the status update and handoff process, which marks the current story Complete and identifies required follow-up actions for the next sprint.

What limitations exist when validating implementation against GDD and ADR references?▼

Validation relies on the presence of GDD/ADR references within the story; if these documentation links are missing or incomplete, the Skill cannot accurately verify criteria or report deviations for sprint tracking.