sprint-plan

sprint-plan is a skill for Claude Code from Donchitos/Claude-Code-Game-Studios. It costs 21 tokens per session (4,875 once invoked), scanned A, original, MIT.

A planner for creating or updating a sprint plan from the current milestone, completed work, project backlog, and team capacity. A milestone is a larger project target made up of smaller tasks or stories.

In plain words
What is it for?
Use it to start a new sprint, revise an existing sprint, or inspect sprint status in a game project.
Why use it?
It turns current project information into an organized set of work for the next development period and keeps planning aligned with available capacity.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents; names the AskUserQuestion tool.

Good fit Use it to start a new sprint, revise an existing sprint, or inspect sprint status in a game project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/donchitos/claude-code-game-studios/sprint-plan
About the project

Claude Code Game Studios is a setup that organizes Claude Code into a coordinated game-development team of specialized AI agents. It supports game projects across design, programming, art, audio, narrative, quality assurance, and production, with skills and workflows for coordinating that work.

Donchitos/Claude-Code-Game-Studios · 26,985 stars · on GitHub

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 Donchitos/Claude-Code-Game-Studios --skill sprint-plan
Clone the repo
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios

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.

agentmods badge for sprint-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/sprint-plan/github.svg)](https://agentmods.dev/skills/donchitos/claude-code-game-studios/sprint-plan)
Your own site
<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/sprint-plan"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/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.

agentmods 80×15 button for sprint-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/sprint-plan"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,875 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 7
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.04875
Opus 5.5 $0.00008 $0.01950
Sonnet 5.5 $0.00004 $0.00975
Haiku 4.5 $0.00002 $0.00487

Measured yesterday against content hash 55b5da9a8180, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 yesterday.

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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

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

How it starts

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

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,story_granularity,workflow

Resolved above — use as-is; --review overrides review_mode. No block → defaults in .claude/docs/config-resolution.md.

Sprint Plan

Existing Sprints

!ls production/sprints/ 2>/dev/null || echo "(no production/sprints/ directory yet)"

Resolved before this skill runs — use it to identify the previous sprint in Phase 1 rather than re-globbing.


Phase 0: Parse Arguments

Extract the mode argument (new, update, or status).

See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

story_granularity — it sets how many stories to allocate per sprint, scaled by velocity: 2–4 at coarse (the default, via rigor: minimal), 6–10 at balanced (rigor: standard), 15–25 at fine. A Ready backlog smaller than the range is planned whole — never padded with invented stories.

Review mode check (before gates run):

  • Use the review mode from the resolved block above (--review overrides it for this run) — do not re-resolve it, and do not ask for it. With nothing configured it follows modes.rigor: solo at minimal, lean at standard.
  • Never write a review mode — not to project.yaml, not to production/review-mode.txt. modes.review_mode is one of the knobs modes.rigor fronts: pinning it in project.yaml shadows the rigor expansion, and the legacy file sits above that expansion, so either write would freeze director-review depth for good. --review covers a one-off. If the user wants a different depth to persist, point them to changing modes.rigor (/settings modes.rigor=<minimal|standard|full>), or to pinning it on purpose with /settings --local modes.review_mode=<full|lean|solo> (a personal override in project.local.yaml).

Read the full file on GitHub · 405 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.

  1. yesterday Changed · +48 lines 55b5da9a8180
  2. 12d ago Changed · +2 lines 42005a68350a
  3. 21d ago Changed · +10 lines 92015a9bf998
  4. 26d ago Changed 3f2b88b42696
  5. 27d ago Changed · +63 lines · -18 tokens per session b269f52b4b79
  6. 1mo ago First seen · 282 lines · 39 tokens per session scan A d402a9f276f8

Subscribe to this mod's changes

sprint-plan is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,985 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 4,875 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

work-log-claude

A work-log generator that reads Claude Code's local session records and produces an evidence-based Markdown report. It can organise work by project and time period while excluding unrelated session data.

ValorVie/custom-skills · 105 tokens

dare-refine

Analisa complexidade de uma task DARE e, quando alta, quebra em sub-tasks menores. Use após gerar o DAG (para tasks HIGH/CRITICAL), quando o dev pedir refinamento manual, ou quando o escopo mudou e uma task ficou grande. Combina heurística determinística (CLI) com decisão semântica do agente.

dewtech-technologies/dare-method · 76 tokens

dare-dag

Mostra o DAG estático de tasks (DARE/dare-dag.yaml): ranks, dependências e caminho crítico. Use dare dag viz para exportar o diagrama. Mapeia o CLI dare dag.

dewtech-technologies/dare-method · 0 tokens

dare-graph

Consulta e visualiza o grafo de conhecimento do projeto (tasks, arquivos, schemas, endpoints, componentes, entidades e suas relações). Mapeia o CLI dare graph.

dewtech-technologies/dare-method · 42 tokens

project-diagnosis

Structured gap analysis that identifies what a project is missing — not what's done poorly (that's /audit), but what's absent entirely. Checks for tests, CI, security basics, linting, type safety, deployment readiness, and dependency health. Each finding has a severity and a concrete fix action.

Vimalk0703/shipworthy · 63 tokens

tech-debt-tracking

Track shortcuts with justifications, prevent debt accumulation, and surface outstanding debt at session start.

Vimalk0703/shipworthy · 24 tokens