Sprint Plan

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 Plan" for me. The skill itself creates, updates or reports on a sprint plan for a game project, in three modes: new, update and status. For a new plan it gathers context (the hand-authored milestone in production/milestones/ when one exists, the previous sprint and its unfinished carryover, the Ready stories found by globbing production/epics/**/story-*.md — with no stories it stops BLOCKED and never invents work — the design documents in design/gdd/, and the risk register when one exists), then generates the plan: sprint goal, a goal-prerequisites check (what showing the goal needs, what is missing, reported but never silently fixed by inventing stories), capacity with a 20 percent buffer, Must Have, Should Have and Nice to Have tables, carryover, risks and a definition of done. It also prepares, but does not yet write, production/sprint-status.yaml, the machine-readable story-status file read by /sprint-status, /story-done and /help. In full review mode only, it spawns the template's producer agent with the PR-SPRINT director gate to judge feasibility (skipped in lean and solo modes); in every mode it then checks for a QA plan and, when none exists, asks explicitly how to proceed before the write ask. Only after the separate "May I write the sprint plan to production/sprints/sprint-NNN.md and production/sprint-status.yaml?" question is answered yes does it write both files together; a no gives verdict BLOCKED. Update mode revises an existing plan and its yaml under the same approval; status mode only generates a report. It resolves review_mode, automation, story_granularity and workflow by running the template's hooks/yaml-helper.sh, outside this skill's folder, and it never writes a review mode anywhere. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/sprint-plan/ 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-plan/ 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 55b5da9a8180dd0d62a6babffd63dc2cbcc6d5156a2dbcc2528b427253a1606e 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 review_mode, automation, story_granularity and workflow, follows .claude/docs/automation-modes.md, config-resolution.md and director-gates.md, reads my project's milestone, sprint, epic, story, design and risk files under production/ and design/, and in full review mode spawns the template's producer agent for the PR-SPRINT gate — agents, docs and project files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its persistent outputs are the sprint plan file in production/sprints/ and production/sprint-status.yaml, written together only after its explicit "May I write" ask (an earlier yes to the QA plan question is never that approval); status mode writes nothing. No third-party service, account or credential is named in the file. - Do not plan or update any sprint, do not spawn the producer agent, do not run any template 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-plan folder into the agent's skills directory, in a folder named exactly "sprint-plan", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: sprint-plan), 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/ and design/ files and can spawn its producer agent), and that at use time it writes the sprint plan and sprint-status.yaml together only after its explicit write ask). 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.