
Dev Story Implementer
Implements one game-dev story in code and tests, following its architecture decisions
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 4 files
What it does
When you ask the agent to build or start a story from a game project's planning docs, this skill makes it check the story is ready (its architecture decision is accepted, dependencies are done), mark the story In Progress after asking you, hand the coding work to a programmer sub-agent with a brief built from the story, then check the result parses and looks right. It also updates the story's status, file list and sprint tracker, with your confirmation for each change.
Great for
- Developers using the Claude Code Game Studios template who work through sprint stories
- Teams that keep stories, ADRs and a sprint-status file in the repo and want consistent progress tracking
Skip it if
- Projects without this studio's story, ADR and manifest structure: the skill expects specific files and scripts and will stop or fail otherwise
- Unreviewed autonomous runs: it can write code, edit story files and run the Godot binary, so reviewing the diff before committing is important
Try asking
- “Implement story production/epics/combat/story-003.md”
- “Start working on the inventory drop story”
- “Build the next story in the current sprint”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 4 original files, the MIT licence and an attribution note.
dev-story.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip dev-story.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip dev-story.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 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
- Confirm the story path and the In Progress change at the prompts, since the skill asks before writing to story and sprint files.
- Run /code-review on the changed files afterwards, and /story-done to close the story.
- Make sure the story's ADR is Accepted and the ADR Version matches before starting, or the skill will stop.
What's inside
- CONTRACT.md
- references/engine-checks.md
- references/version-mismatch.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.