skills.rest
FrancisVarga
FrancisVargaCOMMUNITY
Explore all skills by this author →
GitHub

story-done

Validate completed game-dev stories against acceptance criteria and evidence gates.

Updated May 13, 2026
Search Tags:#code review#acceptance criteria#ADR compliance#test evidence#story completion#sprint workflow#GDD validation
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill story-done-francisvarga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/story-done
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill story-done-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stories from being marked complete when the implementation fails acceptance criteria, drifts from the current GDD/ADR requirements, or lacks the required evidence and review gates.

Core Features & Use Cases

  • End-of-story verification: Reads the story file, extracts acceptance criteria, required artifacts, and referenced TR/ADR details, then checks whether the implementation matches.
  • Acceptance-criterion gating with traceability: Automatically verifies objective criteria (e.g., file/test/config evidence) and uses targeted confirmations for subjective criteria, while producing a criterion-to-test traceability table.
  • Deviation and readiness checks: Flags GDD rule drift, manifest version staleness, ADR constraints issues, hardcoded-value risks, and scope creep, then runs QA and code-review gates depending on mode.
  • Closure + status updates: Updates the story status to Complete, records completion notes, updates sprint/session state, optionally logs tech debt, and surfaces the next ready story.

Quick Start

Run story-done with the path to the story you just implemented to verify criteria, gates, deviations, and close it properly.

Frequently Asked Questions about story-done

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

FAQPage Schema
How do I verify story completion against acceptance criteria before closing a sprint ticket?▼

Story completion verification reads the story file, extracts acceptance criteria, cross-checks referenced TR and ADR details, and confirms implementation matches requirements before closing. This prevents stories from being marked complete when the implementation drifts from design requirements.

What is the best way to check for GDD rule drift and ADR compliance when finishing a story?▼

GDD rule drift and ADR compliance checks flag manifest version staleness, hardcoded-value risks, and scope creep during story closure. The process cross-references the story file against the current GDD and ADR constraints to ensure implementation stays aligned with documented decisions.

How do I generate a criterion-to-test traceability table for code review gates?▼

A criterion-to-test traceability table maps objective criteria to file, test, or config evidence automatically, while using targeted confirmations for subjective criteria. This traceability is produced during the end-of-story verification process to satisfy QA and code-review gates.

Can I run story closure verification in solo mode for independent game development workflows?▼

Story closure verification supports lean, full, and solo review modes for coordinated sprint workflows. Solo mode allows independent developers to run QA and code-review gates, verify acceptance criteria, and update sprint metadata without requiring a separate reviewer.

Does story closure update sprint metadata and log technical debt automatically?▼

Story closure updates the story status to Complete, records completion notes, updates sprint and session state, and optionally logs technical debt. After closing, it surfaces the next ready story to maintain continuous workflow momentum.

Why does story completion fail when test evidence is missing for acceptance criteria?▼

Story completion fails when test evidence is missing because acceptance-criterion gating requires objective proof of implementation. The verification process checks for file, test, or config evidence to ensure the story meets its design requirements before allowing status updates.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
slgoodrichslgoodrich
121

user-story-templates

Generate user story templates with acceptance criteria and INVEST validation.

Community
Basic
polsegupolsegu

story-done

Verify story implementation against acceptance criteria and design documents.

Community
Advanced
polsegupolsegu

propagate-design-change

Cross-reference ADRs and traceability index to identify impacted architectural decisions from revised GDDs.

Community
Advanced