
Sprint Status Snapshot
Gives a quick read-only burndown and risk snapshot of the current game sprint or build order.
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 1 file
What it does
When you ask how the sprint is going, the agent reads your sprint plan and story files, works out how much time is left, and checks which stories are complete, in progress, blocked, or not started. It then gives a short summary of about 30 lines with at most one recommendation. It is strictly read-only: it does not edit files or propose changes. It is built for a game-development workflow that uses a project folder layout with production/sprints and story files.
Great for
- Game or software teams using the Claude Code Game Studios structure who want a fast progress check
- Solo developers working through a one-page build order who want to know the next story to do
- Leads who want a quick situational check before using heavier sprint-management commands
Skip it if
- Full sprint reviews or planning, since the skill itself points users to /sprint-plan and /milestone-review for that (it is only a snapshot)
- Projects without the expected production/sprints or story file layout, where it will just report that files are missing
Try asking
- “How is the sprint going?”
- “/sprint-status 3”
- “What is the next story I should work on in the build order?”
- “Show me the burndown and any emerging risks for the current sprint.”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
sprint-status.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip sprint-status.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip sprint-status.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
- Keep production/sprint-status.yaml updated so the skill reads authoritative status instead of guessing from markdown.
- Run it with no argument for the current sprint, or pass a sprint number like 3 to check a specific one.
- Treat its single recommendation as a prompt; it does not change anything, so you decide the next step.
What's inside
- 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.