sprint-plan
Skill9 starsChanged 7 months agoMITView on GitHub
Create a sprint plan from the systems-index and current priorities. Breaks features into tasks with estimates and owners.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- mehboobali98/rmine-skillstheir own version, first seen Nov 6, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use playtest-report and team-audio.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 4 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 4 projects that use this
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- faizkhairi/claude-code-blueprint★ 73same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- a-lottes/aSPARK★ 25same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
26 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read production/decision-log.md (if exists)
- Very specific: line 26
Check open bug tickets (production/bugs/ if tracked here)
- Very specific: line 32
Content-focused: Add maps/quests/items to existing systems
- Very specific: line 45
Use /estimate for each task
- Very specific: line 51
Write to production/sprints/sprint-<N>-plan.md using .claude/docs/templates/sprint-plan-template.md.
- Very specific: line 65
Add sprint plan filename to production/session-state/current-sprint.txt.
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/sprint-plan — Sprint Planning Workflow
Delegate to: producer
Prerequisites
design/gdd/systems-index.mdexists (run/map-systemsfirst if not)- Current sprint context in
production/session-state/(if any)
Steps
1. Ask Planning Context
- "What's the sprint length?" (default: 2 weeks)
- "What's the theme/goal for this sprint?"
- "Any hard deadlines or events driving priorities?"
- "What went well / poorly last sprint?" (if returning)
2. Review Backlog
- Read
design/gdd/systems-index.md - Read
production/decision-log.md(if exists) - Read
production/risk-register.md(if exists) - Check open bug tickets (
production/bugs/if tracked here)
3. Propose Sprint Goals
Present 2-4 sprint theme options based on priorities:
- Feature-focused: Ship N new features
- Quality-focused: Polish existing, fix bugs, reduce tech debt
- Content-focused: Add maps/quests/items to existing systems
- Infrastructure-focused: Refactor, CI/CD, tools
- Live-ops-focused: Events, balance tweaks, retention features
4. Break Into Tasks
For the chosen theme, break into tasks:
- Design tasks: GDDs to write/update
- Implementation tasks: Code to write
- Art tasks: Assets needed
- QA tasks: Tests to run
- Polish tasks: Fixes and improvements
5. Estimate & Assign
- Use
/estimatefor each task - Assign each to a specialist (not a human, but the agent that would own it)
- Flag dependencies
- Sum total effort; verify it fits sprint capacity
6. Generate Sprint Plan Document
Write to production/sprints/sprint-<N>-plan.md using .claude/docs/templates/sprint-plan-template.md.
Sprint Plan Template Sections
- Sprint Goal (1-2 sentences)
- Duration (start date, end date)
- Theme
- Committed Tasks (list with estimates and owners)
- Stretch Goals (if capacity allows)
- Risks (known blockers, unknowns)
- Definition of Done (what "sprint complete" means)
- Review Cadence (when to check progress)
Output
Present the draft plan to the user for approval. On approval, save to disk.
Add sprint plan filename to production/session-state/current-sprint.txt.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

