A workflow for turning a game's systems list and priorities into a sprint plan. A sprint is a short development period with a focused set of goals, tasks, estimates, and owners.

Use it to choose sprint goals, review the backlog, divide design and coding work into tasks, and assign estimates and owners.

It gives the team a practical order of work and accounts for decisions, risks, bugs, deadlines, and lessons from the previous sprint.

sprint-plan — Skill for Claude Code by CodePhobiia

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add CodePhobiia/claude-roblox-game-studio --skill sprint-plan

Clone the repo

git clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/sprint-plan/github.svg)](https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/sprint-plan)

Your own site

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/sprint-plan"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/sprint-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/sprint-plan"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 595 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.00595
Opus 5	$0.00013	$0.00298
Sonnet 5	$0.00005	$0.00119
Haiku 4.5	$0.00003	$0.00060

Measured 9d ago against content hash 0fcd5cfd8fd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sprint-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/sprint-plan/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sprint-plan — Sprint Planning Workflow

Delegate to: producer

Prerequisites

design/gdd/systems-index.md exists (run /map-systems first 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 /estimate for 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)

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 66 lines · 26 tokens per session scan A 0fcd5cfd8fd4

Subscribe to this mod's changes

sprint-plan is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 595 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Game development Project management

gate-check

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.

Donchitos/Claude-Code-Game-Studios · 64 tokens

setup-engine

Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

Donchitos/Claude-Code-Game-Studios · 45 tokens

day-one-patch

Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.

Donchitos/Claude-Code-Game-Studios · 63 tokens

sprint-plan