Sprint Status

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Sprint Status" for me. The skill itself is a fast situational awareness check, not a sprint review: it reads the current sprint plan and story files, scans for status markers, and produces a concise snapshot. It finds the sprint file in production/sprints/ (the argument, or the most recently modified), reads production/sprint-status.yaml directly when it exists — the authoritative source of truth — and only falls back to scanning the story files' status markers when the yaml is absent, saying so in its output. It calculates days remaining from the sprint dates, detects stale in-progress stories (a story whose Last Updated date is more than 4 days old; a story with no date is reported as never stamped, never silently treated as stale), and assesses the burndown by comparing completion percentage to time consumed (On Track, At Risk or Behind, with any stale story upgrading the verdict to at least At Risk). Its output is a short report: progress table with every story's priority, status, owner and blocker, an attention-needed table for stale stories, must-haves at risk, emerging risks and exactly one concrete recommendation at most. When production/sprints/ does not exist at minimal workflow, it instead reports progress through the brief's build order using the story list the template's story-status.sh script printed before the skill body was read. The skill is strictly read-only: it does not update the sprint plan, does not change any story status, and does not propose scope cuts. It resolves story_granularity and workflow by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: haiku. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/sprint-status/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/sprint-status/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 34d09121606a14f6b5c5a82cafe65796f97adb4ed8ed8857554384ae6fe90a14 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve story_granularity and workflow, reads my project's sprint plans in production/sprints/, production/sprint-status.yaml and the story files under production/epics/, and at minimal workflow relies on the template script .claude/scripts/story-status.sh, whose output is printed into the session before the skill body is read — the hook and the script live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. - At use time it writes nothing at all: it is read-only by design, it updates no sprint plan and no story status, and it makes at most one recommendation. No third-party service, account or credential is named in the file. - Do not check any sprint status, do not run the template's story-status script or hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole sprint-status folder into the agent's skills directory, in a folder named exactly "sprint-status", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: sprint-status), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook, reads the template's production/ files and can rely on its story-status.sh script), and that at use time it is strictly read-only and writes nothing). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.