Estimate team capacity and select committed backlog stories for a sprint.
npx skills add https://github.com/omeragaakbas/zoyare --skill sprint-plan-omeragaakbas
Please help me install this Agent Skill. Skill: sprint-plan Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/sprint-plan Command: npx skills add https://github.com/omeragaakbas/zoyare --skill sprint-plan-omeragaakbas
Plan sprints with realistic scope by estimating team capacity, selecting stories that meet the Definition of Ready, sequencing dependencies, and identifying risks so teams avoid overcommitment and missed objectives.
Plan a two-week sprint for the Payments team using the backlog file and the last three sprints' velocity to produce a sprint goal, committed stories with points and owners, capacity calculations, dependencies, and a risk mitigations list.
High-intent search queries and answers about installing and using this skill.
Estimate team capacity for sprint planning by calculating available story points from team size, individual availability, and historical velocity, while applying a 15-20% buffer to prevent overcommitment and missed sprint objectives.
Capacity-aware sprint planning is the process of selecting committed backlog stories based on actual team availability. A buffer is needed to absorb uncertainties and high-risk items, ensuring the team avoids overcommitment and meets the sprint goal.
Map dependencies and flag risks during backlog selection by sequencing dependent work, identifying the critical path, assigning external owners, and proposing mitigations for high-uncertainty items before committing them to the sprint plan.
You can use this sprint planning approach for a two-week sprint by factoring in PTO, meetings, and on-call rotations to calculate net capacity, ensuring selected stories align with realistic team availability and historical velocity.
A sprint plan summary should include a sprint goal, duration, calculated team capacity, committed stories with points and owners, a buffer percentage, and a risk-to-mitigation list to avoid overcommitment and track known external dependencies.
Stop pulling prioritized stories during capacity estimation when the cumulative story points reach the available team capacity, ensuring each story meets the Definition of Ready and flagging any remaining items needing backlog refinement.
xloxn69Generate a balanced Markdown sprint plan from backlog stories and team capacity.
skytiger6724Plan sprint capacity, story selection, dependencies, and risks for upcoming delivery windows.
Nir-BhayGuide backlog refinement sessions using the DEEP framework and Planning Poker.
YoshikemoloAnalyze Jira velocity and capacity to forecast sprint outcomes.
