Back to Skills
Planning

Sprint Planning Assistant

Creates a sprint plan with goals, capacity, and committed work

/sprint-planning-assistant

Time Saved

2 hrs → 10 min

Compared to doing it manually

Slash Command

/sprint-planning-assistant

Type this in Claude to run the skill

The Problem

Sprint planning meetings drag on for hours, teams overcommit, and sprint goals are vague or non-existent. By the time planning is done, everyone is exhausted.

What You Get

  • Clear sprint goal (one sentence)
  • Capacity table with availability
  • Committed work backlog
  • Stretch goals
  • Dependencies and risks identified
  • Definition of done

How to use this skill

  1. 1Download the skill file using the button on this page
  2. 2Add the file to your .claude/skills/ folder in your project
  3. 3Type /sprint-planning-assistant in Claude to run the skill

Best For

Sprint kickoffsAgile teamsScrum planning

Frequently Asked Questions

Start with sprint goal (what outcome you're targeting). Pull items from the prioritized backlog. Estimate capacity, not velocity. Leave buffer for unknowns (15-20%). End with clear commitments and owners.

Commit to 70-80% of capacity. Over-commitment leads to burnout and carryover. Under-commitment wastes potential. Track velocity over time to calibrate. It's better to finish early than carry over.

Grooming prepares items (clarifying requirements, estimating, splitting stories). Planning selects items for the sprint and confirms commitment. Grooming is ongoing; planning happens at sprint start.