A sprint-planning tool for choosing which backlog items a team will complete during a fixed period. It records the sprint goal, committed work, dates, risks, and the starting scope used for a burndown chart.

Use it at a sprint boundary to check past capacity, select ready items, assign them to the sprint, and create the sprint plan.

It turns a long backlog into a clear, agreed work plan and gives progress tracking a fixed baseline.

plan-sprint — Skill for Claude Code by atman-33

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 atman-33/workhub --skill plan-sprint

Clone the repo

git clone --depth 1 https://github.com/atman-33/workhub

Made for: Claude Code.

Or install team-ops, the plugin that ships this one along with the rest of its 13 skills.

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/atman-33/workhub/plan-sprint.svg)](https://agentmods.dev/skills/atman-33/workhub/plan-sprint)

Your own site

<a href="https://agentmods.dev/skills/atman-33/workhub/plan-sprint"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/plan-sprint.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 426 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.00050	$0.00426
Opus 5	$0.00025	$0.00213
Sonnet 5	$0.00010	$0.00085
Haiku 4.5	$0.00005	$0.00043

Measured 4d ago against content hash 01e00924730a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

plan-sprint 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 4d 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.

plugins/team-ops/skills/plan-sprint/SKILL.md · 41 lines

What it actually says

Plan a sprint

Creates projects/<p>/sprints/<sprint-id>/ with the human-readable plan and the machine-readable scope that daily burndown tracking is measured against.

Steps

Sprint id: <year>.<sequence> (e.g. 2026.15) — sortable; next sequence = latest existing + 1. Length comes from project.json (sprint.lengthDays).
Velocity check: from backlog/progress-history.jsonl and previous sprints' scope vs done, tell the user roughly how many points fit.
Select scope with the user: walk product-backlog.md top-down; candidates need story + AC + points (send gaps to manage-backlog first). Set each committed item's sprint: frontmatter.
Write the outputs:
- planning.md (team content language): sprint goal, dates, committed items table, risks/dependencies.
- scope.json (burndown baseline — do not edit afterwards except via a documented scope change):
```
{
  "sprint": "2026.15",
  "start": "<date>", "end": "<date>",
  "items": [{ "id": "P-0012", "points": 3 }]
}
```
Append an activity-log line, then remind the user the daily routine (sync → snapshot → report) starts drawing the burndown from tomorrow.

Scope changes mid-sprint

Append the added/removed item to scope.json and record the change with a date in planning.md — the daily report annotates these.

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.

4d ago First seen · 41 lines · 50 tokens per session scan A 01e00924730a

Subscribe to this mod's changes

plan-sprint is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 426 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.

Claude Code Planning Project management claude-code-plugin cross-platform desktop-app developer-tools obsidian

gonavi-cli

Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…

Syngnat/GoNavi · 144 tokens

shipyard-executing-plans

Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…

lgbarn/shipyard · 78 tokens

shipyard-writing-plans

Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague…

lgbarn/shipyard · 96 tokens

plan-sprint