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 selects prioritized backlog items, defines a single measurable Sprint Goal, and commits only to work that fits team capacity. ## Core Features & Use Cases - Sprint Goal Definition: Guides creation of a unique, measurable, business-focused Sprint Goal that unifies the selected items. - Capacity-Based Selection: Enforces the rule that total story points must not exceed historical velocity, using Fibonacci estimation (1, 2, 3, 5, 8, 13) and flagging 13-point items for decomposition. - Sprint Backlog Construction: Decomposes each selected item into technical tasks of one day or less and produces a capacity plan accounting for availability and absences. - Use Case: At the start of a Sprint for an e-commerce project, use this Skill to pull the top prioritized user stories, set a goal like "the buyer can complete checkout end-to-end with Mercado Pago", estimate in story points, and confirm the commitment fits the team's velocity. ## Quick Start Run the scrum-sprint-planning skill to plan the next Sprint from the prioritized product backlog in docs/source/requisitos/historias-usuario.
