Guide · Agent skill
How to use the Dev Story Implementer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The dev-story skill is an agent skill for Claude Code that implements one story from a game project's planning docs. It checks the story is ready, marks it In Progress after asking you, hands the coding to a programmer sub-agent, then checks the result and updates the story's status, file list and sprint tracker. This guide explains what an agent skill is, how to install this one, how to trigger it, and what to review before you commit.
Dev Story ImplementerDonchitos/Claude-Code-Game-Studios · MIT Download the skill Quick start
- 1Download and unzip. Download the dev-story ZIP from this page and unzip it so the dev-story folder is present.
- 2Place the folder. Copy the dev-story folder into ~/.claude/skills/ for all projects, or into the project's .claude/skills/ folder for one project.
- 3Check the project structure. Confirm the repository has the story, ADR and architecture docs and the scripts under .claude/scripts and .claude/hooks that the skill needs.
- 4Make the story ready. Make sure the story's ADR is Accepted and its dependencies are complete, or be ready to decide how to handle them.
- 5Ask for the story. Tell Claude Code to implement a story, giving its path or describing it.
- 6Confirm the status change. When asked, approve or decline marking the story In Progress.
- 7Review and commit. Read the diff and the updated ## Files section, then run /story-done on the story.
What is an agent skill and what does dev-story make the agent do?
An agent skill is a folder with a SKILL.md file that tells the agent how to carry out a specific task. When you ask for that task in natural language, the agent loads the instructions and follows them.
When you ask the agent to build or start a story, dev-story makes it check the story is ready: its architecture decision (ADR) is accepted and its dependencies are done. After you confirm, it marks the story In Progress and hands the coding work to a programmer sub-agent with a brief built from the story. Afterwards it checks that the result parses and looks right, then updates the story's status, file list and sprint tracker, asking you to confirm each change.
- Checks the story can start (ADR status, dependencies, manifest)
- Asks before marking the story In Progress
- Delegates code and tests to a programmer sub-agent
- Checks the result parses and looks right
- Updates the story Status, Last Updated and ## Files, and its sprint-status.yaml entry, with your confirmation
Install the dev-story skill from the ZIP
Download the ZIP for the skill from this page and unzip it. The skill is in the .claude/skills/dev-story folder of the Donchitos/Claude-Code-Game-Studios repository. Put the dev-story folder in one of two places: ~/.claude/skills/ to make it available in all your projects, or a project's .claude/skills/ folder to make it available only in that project.
If you use the Claude apps instead of Claude Code, you can upload the skill under Settings → Capabilities → Skills.
- Personal install: place the dev-story folder in ~/.claude/skills/
- Project install: place the dev-story folder in your project's .claude/skills/
- Claude apps: upload it under Settings → Capabilities → Skills
Set up the project files the skill expects
The skill is built for the Claude Code Game Studios structure. It expects story, ADR and architecture docs in their expected folders, and repository scripts under .claude/scripts and .claude/hooks: story-facts.sh, adr-status.sh, md-section.sh, session-state.sh, review-receipts.sh and yaml-helper.sh. Stories live under production/epics/, and the sprint file is production/sprint-status.yaml.
Godot must be installed, because the skill is allowed to run godot commands. Projects without this structure will not work with the skill: it expects specific files and scripts and will stop or fail otherwise.
- Claude Code with a Bash shell
- Godot available on the command line
- Story files under production/epics/
- ADR and architecture docs, including docs/architecture/tr-registry.yaml for the full tier
- Optional: production/sprint-status.yaml for sprint tracking
Trigger the skill with a natural request
The skill runs when you say you want to build, implement or start working on a story. You can name the story by its path. If you type nothing after the skill name, the agent takes the story recorded in the session checkpoint at production/session-state/active.md and asks you to confirm it. If there is no checkpoint, it lists the stories with TODO status as options.
It does not run for checking readiness beforehand or for closing the story afterwards. Those are separate tasks.
- "Implement the story at production/epics/combat/story-003.md"
- "Start working on the next combat story"
- "Build the story about enemy spawning"
- "Continue with the story I was working on"
- Not for: "Is this story ready?" or "Close out the story I finished"
Walk through a typical run
The agent first reports the tier it is using, for example Tier: workflow [value], then runs the prerequisite checks. For each change to a file, it asks you first. A typical run asks once to mark the story In Progress, hands the work to a programmer agent, and then reports a summary.
If a dependency is not Complete, the agent asks how to proceed: accept the risk, stop to finish the dependency first, or mark the dependency Complete if it was done but never updated. Declining the In Progress change means the story is not marked, and the run continues.
- Phase 1: find the story and resolve the tier
- Phase 2: check ADR, manifest and dependencies
- Phase 3: ask to mark the story In Progress
- Phase 4: choose the programmer and engine specialist
- Phase 5: hand out the work with a full brief
- Phase 6: parse check, run and look, one Run result line
- Phase 7: summary, ## Files update, checkpoint and next step
Review the changes and what the skill can run
The skill can write code, edit story files and run the Godot binary. Review the diff before you commit. The skill's allowed tools include Bash commands for the repository scripts, godot commands, and creating folders under production/qa/evidence/. It does not use the network.
At the end, the skill points you to the next step: /story-done [story-path], and at standard and full tiers, /code-review first.
- Read the diff before committing
- Check that each file change matches a confirmation you gave
- Runs scripts and the Godot binary; no network use
- Next step is /story-done, after /code-review at standard and full tiers
What people use it for
- Working through sprint stories in a Godot game project that uses the Claude Code Game Studios structure
- Keeping story Status, Last Updated and the sprint-status.yaml entry in step as code is written
- Handing a story's coding to a programmer sub-agent with a brief built from the story's own text
- Catching a story whose ADR is still Proposed or whose dependencies are unfinished before any code is written
Frequently asked questions
How do I install the dev-story skill?
Download the ZIP from this page and unzip it. Put the dev-story folder in ~/.claude/skills/ for all your projects, or in a project's .claude/skills/ folder for one project. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
What does the dev-story skill require?
It requires Claude Code, a Bash shell, and Godot, since the skill is allowed to run godot commands. The repository also needs the scripts under .claude/scripts and .claude/hooks, plus story, ADR and architecture docs in the expected folders.
Is dev-story free to use?
The source is licensed under MIT. This page does not state any price, so check the repository for licence terms and any costs of the tools it depends on, such as Claude Code and Godot.
Can I use dev-story without the Claude Code Game Studios template?
Not reliably. The skill expects specific files and scripts, and it will stop or fail in projects that lack this studio's story, ADR and manifest structure.
Why does the skill ask me before every change?
It is designed to ask for confirmation before changing a story's Status, Last Updated, ## Files or sprint-status.yaml entry, and before writing data files. Declining the In Progress change means the status is left alone and the run continues.
Does dev-story use the internet?
No. The source states that the skill does not use the network. It does run scripts and can run godot commands, so review its changes before committing.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use dev-story if you build a Godot game with the Claude Code Game Studios structure and work through sprint stories with ADRs and a sprint-status file. Pick something else if your project lacks that structure, or if you want an agent to run unreviewed, since the skill can write code, edit story files and run Godot.
Download the skill