sprint-planning

Plans a sprint by scoping work, estimating capacity, setting goals, and drafting a sprint plan document. It is intended for kicking off a new sprint, sizing a backlog against team availability while accounting for PTO and meetings, deciding what is P0 versus stretch, and handling carryover from the previous sprint. It accepts a sprint name or date range as an argument.

The skill is designed to work in two tiers. Standalone, it always defines sprint goals and success criteria, estimates team capacity accounting for PTO and meetings, scopes and prioritizes backlog items, identifies dependencies and risks, and generates a sprint plan document. When tools are connected, it is supercharged: a project tracker can pull the backlog, create the sprint, and assign items; a calendar can account for PTO and meetings in capacity; and a chat tool can share the sprint plan with the team. To run, it asks for the team and availability, sprint length, prioritized backlog, any carryover from last sprint, and cross-team dependencies.

The output is a structured sprint plan in markdown that includes the sprint name, dates, team size, and a one-sentence sprint goal, followed by a capacity table (available days, allocation, and notes per person), a prioritized sprint backlog table (P0/P1/P2 items with estimates, owners, and dependencies), a planned-capacity-versus-load summary, a risks table, a Definition of Done checklist, and a key dates table. Practical tips reinforce the method: plan to 70-80% capacity to leave buffer for interrupts, hold to one clear sprint goal statable in a single sentence, identify stretch items to cut if work runs long, and carry over honestly by understanding why something did not ship before re-committing.