agentmods.dev

sprint-plan

sprint-plan is a command for Claude Code from CrashBytes/claude-role-skills. It costs 11 tokens per session (347 once invoked), scanned A, original, Apache-2.0.

A sprint-planning assistant that uses team capacity, goals, and backlog items to propose a workable sprint. A backlog is the ordered list of planned work, and capacity is the amount the team can realistically complete.

In plain words
What is it for?
Use it to calculate capacity, define a business-focused sprint goal, select backlog stories, flag incomplete work descriptions, and produce a sprint plan.
Why use it?
It reduces overcommitting by accounting for time off, meetings, past delivery speed, missing estimates, acceptance criteria, and dependencies.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the role-based-skills plugin — 7 skills, 15 commands shipped together

not rated 6repo 6mo ago A scan 11 tokens original Apache-2.0

Good fit Use it to calculate capacity, define a business-focused sprint goal, select backlog stories, flag incomplete work descriptions, and produce a sprint plan.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/crashbytes/claude-role-skills/sprint-plan
View source ↗ CrashBytes/claude-role-skills
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.

Clone the repo
git clone --depth 1 https://github.com/CrashBytes/claude-role-skills

Made for: Claude Code.

Or install role-based-skills, the plugin that ships this one along with the rest of its 7 skills, 15 commands.

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/commands/crashbytes/claude-role-skills/sprint-plan/github.svg)](https://agentmods.dev/commands/crashbytes/claude-role-skills/sprint-plan)
Your own site
<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/sprint-plan"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/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/commands/crashbytes/claude-role-skills/sprint-plan"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 347 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00347
Opus 5 $0.00005 $0.00173
Sonnet 5 $0.00002 $0.00069
Haiku 4.5 $0.00001 $0.00035

Measured 9d ago against content hash b757bd0f032a, 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 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.

commands/sprint-plan.md · 43 lines

What it actually says

Sprint Planning

Facilitate a sprint planning session for the team.

Arguments

Sprint context provided: $ARGUMENTS

Workflow

  1. Gather context

    • If a project management MCP server is connected (Jira, Linear, Azure DevOps, GitHub, GitLab), fetch the current backlog and previous sprint velocity
    • If no MCP server, ask the user for: team size, sprint duration, average velocity, and backlog items

  2. Calculate capacity

    • Formula: Available days × Team members × Focus factor (0.7) = Capacity in person-days
    • Account for holidays, PTO, and meetings
    • Convert to story points using the team's historical ratio

  3. Define sprint goal

    • Propose a sprint goal that ties to a business outcome
    • Format: "By the end of this sprint, [stakeholder] will be able to [capability]"
    • The goal should be achievable within the calculated capacity

  4. Select stories

    • Pull from the top of the prioritized backlog
    • Stop when total story points approach 85% of capacity (leave buffer)
    • Flag any stories missing acceptance criteria or estimates
    • Identify dependencies between selected stories

  5. Output sprint plan

    • Sprint goal
    • Capacity calculation breakdown
    • Selected stories with estimates
    • Dependencies and risks
    • Stretch goals (next 2-3 stories if capacity allows)
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. 9d ago First seen · 43 lines · 11 tokens per session scan A b757bd0f032a

Subscribe to this mod's changes

sprint-plan is a command published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 347 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-08-31.

Claude CodePlanningProject managementagent-skillsclaude-pluginclaude-skillsinfosec
Related

Other commands, from other repositories

contribute-to

Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.

MadaraUchiha-314/the-loop · 38 tokens

create-ticket

Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.

MadaraUchiha-314/the-loop · 32 tokens

finish-tasks

Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.

MadaraUchiha-314/the-loop · 23 tokens

work-status

Report the current status of a work item by reading its spec files (requirements/design/tasks) and execution log. Read-only.

MadaraUchiha-314/the-loop · 25 tokens

ledger-check

Audit all ledger files for drift (report; fix only on request).

nunoamorim99/agile-ledger · 14 tokens

triage-bug

Turn bug Inbox reports into registered, prioritized bugs (separate from /triage).

nunoamorim99/agile-ledger · 17 tokens