New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Story Done

by Donchitos in Donchitos/Claude-Code-Game-Studios

End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

MITAuto-check: notesDevelopment

Install Story Done

skills CLI
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill story-done -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Donchitos/Claude-Code-Game-Studios story-done --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/story-done .claude/skills/story-done && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
story-done
GitHub stars
26k
Token cost
~1.2k tokens
SKILL.md length
579 words
Files
10 (incl. references)
Skills in repo
73
Repo updated
First seen
Licence
MIT

At a glance

End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

  • Works in 8 steps: Find the Story → Read the Story → Verify Acceptance Criteria → …
  • Tasks that involve Game design
  • SKILL.md covers Phase 1: Find the Story, Phase 2: Read the Story, Phase 3: Verify Acceptance… and Phase 4: Check for Deviations, plus 6 more sections
  • Calls bash

What it does

Story Done is an agent skill from Donchitos/Claude-Code-Game-Studios. End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `CONTRACT.md`, `references/1-find-story.md` and `references/2-read-story.md`).

It sits in Development, covering Game design, Architecture decision records and Code review. The repository describes itself as: Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy. The licence is MIT.

When your agent uses it

  • Tasks that involve Game design
  • Tasks that involve Architecture decision records
  • Tasks that involve Code review

Example prompts

  • “/story-done”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion, Agent, Bash(bash "*/.claude/skills/story-done/../../hooks/yaml-helper.sh" resolve_config *)

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Find the Story
  2. Read the Story
  3. Verify Acceptance Criteria
  4. Check for Deviations
  5. Lead Programmer Code Review Gate
  6. Present the Completion Report
  7. Update Story Status
  8. Surface the Next Story

What it can do on your machine

Read from SKILL.md and the folder at commit be8993b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash
    • Write
    • Edit
    • AskUserQuestion
    • Agent
    • Bash(bash "*/.claude/skills/story-done/../../hooks/yaml-helper.sh" resolve_config *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Story Done loads about 1.2k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 36 tokens; SKILL.md has 579 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion, Agent, Bash(bash "*/.claude/skills/story-done/

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Donchitos/Claude-Code-Game-Studios at commit be8993b, republished under its MIT licence (© Donchitos). 579 words, ~1,162 tokens.

Download SKILL.mdSave it as .claude/skills/story-done/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
story-done
description
End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.
allowed-tools
Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion, Agent, Bash(bash "*/.claude/skills/story-done/../../hooks/yaml-helper.sh" resolve_config *)
argument-hint
[story-file-path] [--review full|lean|solo]
user-invocable
true
disable-model-invocation
true
model
sonnet

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,story_granularity,qa.level,testing.strict,system_overrides

Resolved above — use as-is; --review overrides review_mode. No block → defaults in .claude/docs/config-resolution.md.

Story Done

This skill closes the loop between design and implementation. Run it at the end of implementing any story. It ensures every acceptance criterion is verified before the story is marked done, GDD and ADR deviations are explicitly documented rather than silently introduced, code review is prompted rather than forgotten, and the story file reflects actual completion status.

Output: Updated story file (Status: Complete) + surfaced next story.

Phase 1: Find the Story

Read references/1-find-story.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 2: Read the Story

Read references/2-read-story.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 3: Verify Acceptance Criteria

Read references/3-verify-criteria.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 4: Check for Deviations

Read references/4-deviations.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 5: Lead Programmer Code Review Gate

Read references/5-code-review-gate.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 6: Present the Completion Report

Read references/6-completion-report.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 7: Update Story Status

Read references/7-update-status.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 8: Surface the Next Story

Read references/8-next-story.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Show full SKILL.md (226 more words)Show less

Collaborative Protocol

In collaborative mode (the default). For guided and autonomous modes, see .claude/docs/automation-modes.md — the rules below describe collaborative behavior. The BLOCKED-override close (Phase 7) always prompts regardless of mode (it's a scope_changes always-ask decision).

  • Never mark a story complete without user approval — Phase 7 requires an explicit "yes" before any file is edited.
  • Never auto-fix failing criteria — report them and ask what to do.
  • Deviations are facts, not judgments — present them neutrally; the user decides if they are acceptable.
  • BLOCKED and NOT ASSESSED verdicts are advisory — the user can override and mark complete anyway; document the risk explicitly if they do. For NOT ASSESSED, the documented risk is that the criterion was never evaluated, not that it failed — record which criteria those were, so the gap is recoverable later rather than closed over.
  • Use AskUserQuestion for the code review prompt and for batching manual criteria confirmations.
  • At minimal: run /dev-story [next-story-path] (/story-done for an In Review one); when every story is Complete, play the build, then /create-stories for more or /settings to raise modes.rigor
  • With a sprint plan: run /story-readiness [next-story-path] to validate the next story before starting implementation
  • If a sprint plan exists and all its Must Have stories are complete: run /smoke-check sprint → /team-qa sprint → /gate-check
  • If tech debt was logged: track it via /tech-debt to keep the register current

© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in .claude/skills/story-done of Donchitos/Claude-Code-Game-Studios.

  • SKILL.md
  • CONTRACT.md
  • references/1-find-story.md
  • references/2-read-story.md
  • references/3-verify-criteria.md
  • references/4-deviations.md
  • references/5-code-review-gate.md
  • references/6-completion-report.md
  • references/7-update-status.md
  • references/8-next-story.md

Open the folder on GitHubat commit be8993b

Compare with similar skills

Story Done next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Story Done compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Story Done this skillDonchitos/Claude-Code-Game-Studios26k—~1.2kAutomated safety check: NotesMIT
Review GitHub PRNVIDIA/OpenShell16k—~1.7kAutomated safety check: PassApache-2.0
RAG Code Reviewlyonzin/knowledge-rag292—~1.8kAutomated safety check: PassMIT
Code ReviewRunoreLab/MahoShojo-Generator166—~425Automated safety check: PassApache-2.0
Ad ReviewCorridorTech/PoseCap224—~2.4kAutomated safety check: NotesApache-2.0
Implement FeatureLog2n-io/Typhon250—~2kAutomated safety check: PassCustom licence

Similar skills

  • Review GitHub PR

    NVIDIA/OpenShell

    Official

    Review a GitHub pull request by summarizing its diff and key design decisions.

    16k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • RAG Code Review

    lyonzin/knowledge-rag

    When performing code review on a PR, diff, snippet, or "look at this change" request, first consult the corpus for related ADRs, coding standards, prior patterns, and similar files.

    292 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Review

    RunoreLab/MahoShojo-Generator

    A skill your agent uses when reviewing MahoShojo-Generator code, a branch, commit range, pull request, or implementation against current behavior and accepted ADR/spec requirements.

    166 GitHub stars~425 tokensUpdated today
    DevelopmentAuto-check passed

  • Ad Review

    CorridorTech/PoseCap

    Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.

    224 GitHub stars~2.4k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

  • Implement Feature

    Log2n-io/Typhon

    Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests…

    250 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Gameplay Design Sync

    tangziwen/CubeMiniGame

    Assess whether completed CubeGame gameplay changes should be reconciled into Doc/GameplayIntent design documents.

    359 GitHub stars~1.5k tokensUpdated 21 days ago
    DevelopmentAuto-check passed

More from Donchitos/Claude-Code-Game-Studios

All 73 skills in this repo

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Dev Story

    Donchitos/Claude-Code-Game-Studios

    Implement a story: ADR guidelines, right programmer agent, code plus test.

    26k GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check: notes

  • Game Asset Audit

    Donchitos/Claude-Code-Game-Studios

    Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

    26k GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed

  • Game Asset Spec Writer

    Donchitos/Claude-Code-Game-Studios

    Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

    26k GitHub stars~5k tokensUpdated 3 days ago
    Auto-check passed

  • Game Balance Check

    Donchitos/Claude-Code-Game-Studios

    Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

    26k GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

  • Structured Bug Reports

    Donchitos/Claude-Code-Game-Studios

    Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

    26k GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check: notes

Categories

Questions about Story Done

What does Story Done do?

End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status. Story Done is an agent skill from Donchitos/Claude-Code-Game-Studios. End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

When should I use Story Done?

Story Done fits situations like: tasks that involve Game design; tasks that involve Architecture decision records; tasks that involve Code review.

How do I install Story Done in Claude Code?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill story-done -a claude-code`. Or copy the skill folder (.claude/skills/story-done in Donchitos/Claude-Code-Game-Studios) into .claude/skills/story-done in your project. Claude Code loads it when a task matches its description.

How do I install Story Done in Codex?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill story-done -a codex`. Or copy the skill folder (.claude/skills/story-done in Donchitos/Claude-Code-Game-Studios) into .agents/skills/story-done in your project. Codex loads it when a task matches its description.

Can I use Story Done in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill story-done -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/story-done, .gemini/skills/story-done, .github/skills/story-done and .opencode/skills/story-done in your project.

What does Story Done need to run?

Going by SKILL.md and its folder, Story Done needs the command-line tools its instructions call (bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion, Agent, Bash(bash "*/.claude/skills/story-done/../../hooks/yaml-helper.sh" resolve_config *).

Does Story Done access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Story Done safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Story Done use?

Story Done is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Story Done use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Story Done?

Skills that share tags, products or a category with Story Done: Review GitHub PR (NVIDIA/OpenShell, 16k stars), RAG Code Review (lyonzin/knowledge-rag, 292 stars), Code Review (RunoreLab/MahoShojo-Generator, 166 stars) and Ad Review (CorridorTech/PoseCap, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Story Done?

Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 26,031 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on October 8, 2026.

Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.