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/workhub

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/github.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/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/atman-33/workhub/plan-sprint"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/plan-sprint.svg" alt="Reviewed on agentmods" width="80" 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.5	$0.00020	$0.00170
Sonnet 5.5	$0.00010	$0.00085
Haiku 4.5	$0.00005	$0.00043

Measured 1mo ago against content hash 01e00924730a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 1mo 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.

1mo 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 (3 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 426 once invoked, about $0.0002 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.

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

expo-launchpad-status

Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.

SummerRiversound/expo-launchpad · 27 tokens

tasknotes

This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…

parisgroup-ai/imersao-ia-setup · 106 tokens

issue-hygiene

How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.

Mikedev115/Aetox · 47 tokens

aetox-slice

Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…

Mikedev115/Aetox · 64 tokens

project-consolidation

Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…

linxule/memex-plugin · 133 tokens

roadmap-update

Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…

evb87-tech/corpus · 94 tokens