sprint-planning

Plan a realistic sprint or short delivery cycle with goal, scope, capacity, dependencies, acceptance criteria, risks, and review signals. Use for sprint planning, iteration planning, backlog selection

SKILL.md

GitHub

Sprint Planning

Plan for a demonstrable outcome, not maximum ticket count.

  1. Set one sprint goal and the user/product outcome it supports.
  2. Review capacity, availability, historical throughput, dependencies, uncertainty, and unplanned-work allowance.
  3. Select work that can reach a tested increment; make acceptance criteria and ownership explicit.
  4. Separate committed, stretch, discovery, and blocked work.
  5. Define review/demo evidence, risk triggers, and what will be de-scoped first if capacity changes.

Do not treat estimates as promises or silently fill a sprint beyond verified capacity.