Overview

Sprint Planning defines the upcoming sprint by selecting stories from the epic backlog, articulating a sprint goal, and ordering work to reflect dependencies and priorities. It helps the team commit to a feasible scope and anticipate blockers.

How This Skill Works

The agent reviews available stories from epics, considers velocity from previous sprints, and selects stories that form a coherent sprint goal. It then validates readiness, orders work by dependency and priority, and defines the sprint goal along with blockers.

When to Use It

• Beginning a new sprint and needing a concrete, achievable goal
• Backlog has many stories and you must choose a cohesive subset for the sprint
• Velocity data from previous sprints is available to set a realistic capacity
• Dependencies or blockers require explicit sequencing and planning
• Need to validate that stories are implementation-ready before committing

Quick Start

1. Step 1: Gather inputs - projectName, sprintNumber, epics, previousSprints
2. Step 2: Review backlog and velocity, then select stories forming a coherent sprint goal
3. Step 3: Validate readiness, set execution order by dependencies, and identify blockers

Best Practices

• Start with a crisp sprint goal aligned to the epic
• Use velocity data from previous sprints to set realistic capacity
• Validate that each chosen story is implementation-ready
• Order stories by dependency and priority to minimize risk
• Identify blockers early and assign owners for resolution

Example Use Cases

• Sprint to deliver a user authentication enhancement with a clear dependency chain from the authentication epic
• Bug-fix sprint following a release, focusing on high-priority defects
• API integration sprint where new stories depend on backend API readiness
• Platform parity sprint to align features across web and mobile with coordinated dependencies
• Refactor sprint targeting code quality improvements with defined blockers and milestones

Frequently Asked Questions