Is Sprint Planning free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Sprint Planning

Q: How do I know the Sprint Planning output is good?

The skill verifies itself against its own quality checks: Sprint goal is outcome-focused (not "implement X" — something like "users can do Y"); Team capacity is calculated using actual availability, not theoretical 100%; Every story has an acceptance criterion (flag any that don't); Stories estimated at 8+ points are flagged for splitting.

🟢 Production-Ready🕐 updated 2026-07-14 ✅ 3.8/5 🔷 SkillSpec L3 ⚙ ships an executable helper pm-delivery

Structure and facilitate sprint planning sessions. Use when asked to plan a sprint, organise backlog items, assign story points, create sprint goals, or prepare sprint planning agendas. Produces a sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and a structured sprint planning meeting agenda.

📚 Based on Scrum — The Scrum Guide (Schwaber & Sutherland)

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

✅ 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.

✓Sprint goal is outcome-focused (not "implement X" — something like "users can do Y")

✓Team capacity is calculated using actual availability, not theoretical 100%

✓Every story has an acceptance criterion (flag any that don't)

✓Stories estimated at 8+ points are flagged for splitting

✓Carry-overs from last sprint are accounted for in capacity

⚠️ What it refuses to do

Do not write sprint goals as task lists — goals must be outcome-focused and scoreable pass/fail at sprint end

Do not commit to 100% of available capacity — always recommend 80% to preserve slack for unplanned work

Do not carry stories with no acceptance criteria into the sprint — flag them as blockers before committing

Do not allow stories estimated at 8+ points into the sprint without splitting them first

Do not ignore carry-over items when calculating capacity — they consume capacity and must be accounted for before new work is pulled in

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-mcp

Example output

Input: Team of 5, 2-week sprint, average velocity 30 points, one engineer out 3 days. Backlog: checkout redesign (8), payment retries (5), analytics events (3), bug bash (3), API rate limiting (5). · generated by claude-sonnet-4-6

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-planning"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Sprint Planning 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