Skip to content
Get packs

Story Done

Verifies a finished game story's acceptance criteria and closes it with a report

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
5 files

What it does

When you say a story is done, this skill makes the agent work through a checklist: it checks each acceptance criterion against evidence in the project (files, tests, design docs and architecture decisions), reports any deviations from the design or scope, and only marks the story Complete after you agree. It is built for a game-studio workflow where work is tracked as numbered stories under epics and sprints, and it writes its results back into those project files.

Great for

  • Game teams using the Claude Code Game Studios template who track work as stories and sprints
  • Developers who want a structured, evidence-based close-out of a story rather than a quick sign-off
  • Leads who want a traceable record of which acceptance criteria were verified and which remain untested

Skip it if

  • Projects without the production/epics story structure and supporting scripts, since the skill depends on them and will fail or stop early
  • Criteria that only a human can judge by playing: the skill will not mark behaviour or feel as passed from reading code, so it cannot replace playtesting
  • Teams wanting an automatic sign-off: it writes story status and may write to the tech debt register, so it should be used with review rather than trusted blindly

Try asking

  • “The login screen story is done, close it out”
  • “Story production/epics/combat/story-003.md is finished --review lean”
  • “Close the current story and log any leftover issues to the tech debt register”
Step-by-step guide: how to use Story DoneInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 5 original files, the MIT licence and an attribution note.

    story-done.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip story-done.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip story-done.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the story file path explicitly to avoid picking the wrong story from the checkpoint
  • Answer criteria honestly: choose Not tested yet rather than Yes when you have not run the build
  • Review the files it writes (story Status, Completion Notes, sprint-status.yaml) before committing them

What's inside

  • CONTRACT.md
  • references/review-gates.md
  • references/sprint-next.md
  • references/tech-debt-row.md
  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.