story-done

Verify implemented stories against acceptance criteria, design constraints, and test evidence.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill story-done-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/story-done
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill story-done-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stories from being marked complete without verifying acceptance criteria, checking implementation against GDD and ADR requirements, confirming test evidence, and documenting unresolved risks.

Core Features & Use Cases

  • Acceptance Verification: Reads the story and validates every acceptance criterion through automated checks, tests, manual confirmation, or explicit deferral.
  • Quality and Scope Gates: Checks required test evidence, design deviations, manifest staleness, ADR constraints, hardcoded values, and out-of-scope changes.
  • Completion Workflow: Produces a traceability-based completion report, prompts for code review and user approval, updates story and sprint status, records session state, and surfaces the next ready story.
  • Use Case: After implementing a Godot gameplay story, use this Skill to verify its requirements, identify missing tests or design deviations, obtain closure approval, and prepare the story for sprint completion.

Quick Start

Use the story-done skill with the path to the implemented story file and an optional review mode to verify and close it.

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 closing a sprint story?

Verifying acceptance criteria before closing a sprint story requires checking each requirement against automated tests, manual confirmation, or explicit deferral. This skill reads story files, validates every criterion, and identifies missing test evidence to prevent premature story closure.

What is the process for checking GDD and ADR compliance during story completion?

Checking GDD and ADR compliance during story completion involves validating implementation files against design constraints and architecture decision records. This skill checks for design deviations, hardcoded values, manifest staleness, and out-of-scope changes to ensure the implementation matches architectural requirements.

How do I generate a traceability report for code review and story approval?

To generate a traceability report for code review and story approval, map acceptance criteria to test evidence and implementation files. This skill produces a completion report, coordinates code review, and records user approval before updating sprint status.

Can I use this for Godot gameplay story verification and sprint tracking?

Yes, you can use this for Godot gameplay story verification and sprint tracking. It is designed for software development workflows involving GDD compliance, checking implementation files, confirming test evidence, updating story status, and surfacing the next ready story within your sprint.

What happens if test evidence is missing or design deviations are found during story closure?

When test evidence is missing or design deviations are found during story closure, the story cannot be marked complete. This skill identifies unresolved risks, flags out-of-scope changes, documents deviations, and requires explicit resolution or deferral before allowing sprint completion to proceed.