A sprint planning tool that selects work from epics and stories and records it in a sprint plan. A sprint is a short, focused development period, usually lasting one or two weeks.

Use it to start a sprint, revise an active sprint, assign known owners, and define the sprint outcome.

It turns a large backlog into a practical set of work for the next sprint and supports updates when priorities or milestones change.

sprint-plan — Skill for Claude Code by cenconq25

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 cenconq25/claude-code-app-studio --skill sprint-plan

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-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/cenconq25/claude-code-app-studio/sprint-plan/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/sprint-plan)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/sprint-plan"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-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/cenconq25/claude-code-app-studio/sprint-plan"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,877 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.00055	$0.01877
Opus 5	$0.00028	$0.00938
Sonnet 5	$0.00011	$0.00375
Haiku 4.5	$0.00006	$0.00188

Measured 6d ago against content hash e8cf57209a28, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 6d 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 · 243 lines

How it starts

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

Sprint Plan

Builds the bridge between epic story backlogs and what gets worked on in the next 1-2 weeks. Decides which stories enter the sprint, who owns them (when team info is known), and what the sprint's outcome target is.

Output: production/sprints/sprint-NNN-<slug>.md

Purpose / When to Run

Run when:

The previous sprint just ended
A new epic is ready to be tackled
A milestone shift requires re-planning
The team wants to update an in-flight sprint (update mode)

Inputs

All epics: production/epics/*/EPIC.md
All stories: production/epics/*/story-*.md
Existing sprints: production/sprints/*.md
Optional production/milestones/*.md
design/concept.md for primary metric context
production/session-state/active.md

Outputs

production/sprints/sprint-NNN-<slug>.md

Phase 1: Mode

If argument is new, create a new sprint. If update, edit the most recent in-flight sprint. If empty, ask:

Prompt: "New sprint or update existing?"
Options: New sprint, Update existing, Show me current sprint first

For Show me current sprint first: dispatch to /sprint-status and exit.

Phase 2: Inventory Backlog & Capacity

2a: Story inventory

Glob production/epics/*/story-*.md and bucket by Status:

Ready
In Progress
Blocked
Complete

Print counts.

2b: Last-sprint signals

If a previous sprint exists, read it. Capture:

Stories planned vs. completed
Velocity (stories or rough hours)
Carry-over

2c: Capacity

Use AskUserQuestion:

Prompt: "How many engineering days are available for this sprint?"
Options: 5 (1-week sprint, 1 dev), 10, 15, 20, Custom (free text)

Convert to a rough story budget (e.g., 1 day = 1-2 stories of typical size). The user can override.

Use AskUserQuestion:

Prompt: "How many designers / QA / data days available?"
Options: Solo dev (none), Designer + QA shared, Full team, Free text

This affects which story types can be parallelized.

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

6d ago First seen · 243 lines · 55 tokens per session scan A e8cf57209a28

Subscribe to this mod's changes

sprint-plan is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,877 once invoked, about $0.0003 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.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens