What problem does it solve? Teams often start Sprints without a clear objective, overcommit beyond their velocity, or pull in unrefined backlog items, leading to missed commitments and spillover. This Skill structures the Sprint Planning event so the team commits to a coherent, capacity-bounded Sprint with a measurable goal. ## Core Features & Use Cases - Sprint Goal Definition: Guides creation of a single, measurable, business-focused Sprint Goal that unifies the selected backlog items. - Capacity-Bounded Selection: Selects prioritized Product Backlog items whose story point total stays within the team's historical velocity, enforcing pull over push. - Estimation & Decomposition: Applies Fibonacci story point estimation (1, 2, 3, 5, 8, 13) and task breakdown into units of one day or less, flagging 13-point items for splitting. - Use Case: At the start of a Sprint for an e-commerce checkout increment, use this Skill to review refined user stories, set a goal like "the buyer can complete a purchase end-to-end with Mercado Pago", estimate each story, and confirm the total fits the team's velocity. ## Quick Start Ask the assistant to run sprint planning for the upcoming Sprint using the prioritized user stories in the backlog and the team's velocity from the last three Sprints.
