A sprint-planning skill for selecting work for the next development sprint. A sprint is a fixed work period; it uses the average completed work from the last three sprints to estimate how much work the team can take.

Use it to plan a named or automatically detected sprint, calculate capacity, carry over incomplete tickets, and assign suitable backlog tasks after the plan is approved.

It carries unfinished tickets forward and fills remaining capacity from the backlog in priority order, while avoiding changes that could break existing sprint assignments.

How SocialGouv/egapro configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SocialGouv/egapro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SocialGouv/egapro/alpha/.claude/skills/plan-sprint/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/SocialGouv/egapro

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/socialgouv/egapro/plan-sprint/github.svg)](https://agentmods.dev/skills/socialgouv/egapro/plan-sprint)

Your own site

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

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

When invoked 939 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 pass 7 Sept 2026

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.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.00939
Opus 5	$0.00039	$0.00469
Sonnet 5	$0.00016	$0.00188
Haiku 4.5	$0.00008	$0.00094

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

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

How it starts

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

/plan-sprint — Planification du prochain sprint

Usage

/plan-sprint — planifie le sprint qui suit le sprint courant (auto-détecté)
/plan-sprint "Sprint 11" — planifie un sprint cible nommé

À lancer en début de planification (typiquement à la fin du sprint courant, après avoir lancé /velocity pour voir la tendance).

Ce que fait le skill

Capacité = moyenne glissante de la vélocité des 3 derniers sprints terminés (Σ Estimate des feuilles Task/Bug livrées : Done ∪ In review).
Report des tickets non livrés du sprint courant (Status ∉ {Done, In review}) → vers le sprint cible. Ils consomment la capacité en premier.
Complétion depuis le backlog : tickets Status ∈ {Backlog, To Do}, sizés, sans sprint, triés par Priorité (P0→P1→P2) puis petits points d'abord (remplit les trous), ajoutés sans jamais dépasser la capacité.

Limite GitHub — création de sprint

L'API GitHub régénère tous les iterationId quand on édite la config d'un champ iteration → cela orphaniserait toutes les assignations Sprint existantes du board (vérifié par test). Donc /plan-sprint ne crée jamais l'itération.

Si le sprint cible n'existe pas encore (exit 4), le skill s'arrête et indique :

Project EGAPRO V2 → ⚙ Settings → champ « Sprint » → « Add iteration » (dates auto-remplies depuis la durée de 14 j), puis relancer /plan-sprint.

Garde donc ~1 sprint d'avance (comme aujourd'hui : Sprint 10 pré-créé) → le skill tourne alors en entièrement automatique.

Exécution

Étape 1 — Plan (lecture seule). Toujours d'abord :

bash scripts/orchestration/plan_sprint.sh "$ARGUMENTS"

Re-rendre la sortie en chat sous forme de tableaux markdown propres (reportés / ajoutés / total vs capacité) + une courte analyse :

Signaler les tickets reportés non sizés (⚠) — leur charge n'est pas comptée ; suggérer de les sizer (/analyse) si la capacité semble fausse.
Si beaucoup de reports saturent déjà la capacité → le sprint est en dette, peu/pas de backlog ajouté : le dire explicitement.

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

4d ago First seen · 58 lines · 78 tokens per session scan A f648c05b2613

Subscribe to this mod's changes

plan-sprint is a skill published in the GitHub repository SocialGouv/egapro (12 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 939 once invoked, about $0.0004 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-04.

Planning 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

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

egapro: Skill for Claude Code