SV
Sprint Velocity Analysis
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Analyze sprint velocity data and produce an engineering team health report covering delivery trends, capacity utilization, and improvement recommendations. Use when asked to analyze sprint velocity, review team delivery health, identify delivery risks, or produce a retrospective data analysis. Produces a velocity trend analysis, health diagnosis table, top improvement recommendations with implementation steps, and a next-sprint capacity forecast.
📚 Based on Scrum — The Scrum Guide (Schwaber & Sutherland)
What to give it
▸Sprint history — for each sprint: sprint name/number, committed story points, completed story points, and number of items carried over to next sprint; ideally 6–8 sprints minimum
▸Team size and any changes — current team size and any additions or departures during the data window
▸Known disruptions — holidays, company all-hands, on-call incidents, or other events that affected specific sprints
▸Cycle time data (optional) (optional) — if available, p50 and p90 cycle time per sprint (time from start to done)
▸Definition of Done — what "completed" means for this team (merged to main? deployed to prod? accepted by PO?)
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Velocity chart is generated from the actual data provided — not a generic placeholder chart
✓Trend diagnosis states a direction (Improving / Flat / Declining / Erratic) with a quantitative basis (trailing vs. leading average)
✓Carry-over root causes are specific categories with counts — not a generic observation that carry-over exists
✓Each of the 3 recommendations includes a named owner, a start date, and a measurable target with a timeframe
✓Next-sprint capacity forecast uses historical average as the baseline and deducts specific known reducers
✓Health diagnosis table uses Red/Yellow/Green with evidence cited in the Evidence column — no unsupported scores
✓If metrics are missing (cycle time, blocker log), the report explicitly calls them out as recommended additions
⚠️ What it refuses to do
Do not generate the velocity chart from placeholder data — it must reflect the actual sprint data provided
Do not diagnose trend direction without computing trailing vs leading averages — "it looks like it's declining" is not a diagnosis
Do not list carry-over as a generic observation — identify root cause categories with counts for the analysis to be actionable
Do not produce recommendations without a named owner, a start date, and a measurable target
Do not score health dimensions without citing evidence in the Evidence column — unsupported Red/Yellow/Green scores are not credible
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="sprint-velocity-analysis"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Sprint Velocity Analysis is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog