Plan a sprint from PMContext and backlog inputs with capacity and dependency mapping.
npx skills add https://github.com/Wcof/PMSkill --skill pm-sprint-wcof
Please help me install this Agent Skill. Skill: pm-sprint Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-sprint Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-sprint-wcof
This Skill helps product and delivery teams turn a prioritized backlog into an executable sprint plan instead of guessing what can fit into an iteration. It prevents overloaded sprints, vague story selection, unmanaged dependencies, and weak goals by grounding planning in PMContext, capacity, and Definition of Ready checks.
Ask the agent to use pm-sprint to plan the next sprint from PMContext, pm-stories, team capacity, and priority order.
High-intent search queries and answers about installing and using this skill.
Sprint planning from a prioritized backlog requires estimating team capacity, validating stories against a Definition of Ready, and mapping dependencies. This ensures the selected scope aligns with velocity and avoids overloaded iterations.
A realistic sprint capacity estimation accounts for team size, member availability, and historical velocity, while applying a fixed 20% buffer. This formula prevents overcommitment by grounding scope in actual team throughput.
Dependency mapping separates internal and external blockers, identifies owners, and highlights the critical path for iteration stories. This process records associated risks to ensure unblocked delivery during sprint execution.
Defining a user-value sprint goal involves summarizing the delivered outcome into a single sentence rather than listing completed stories. This keeps the iteration focused on product impact and traceable objectives.
Definition of Ready checks are required before pulling stories into a sprint plan to exclude unclear, blocked, or oversized items. Validating DoR ensures only executable stories enter the iteration scope.
Managing sprint scope with velocity fluctuations requires applying a fixed capacity formula with a 20% buffer and validating story sizes. This approach grounds scope decisions in defendable historical data rather than estimates.
GustaPaesValidate and close product backlog stories for sprint readiness.
xloxn69Generate a balanced Markdown sprint plan from backlog stories and team capacity.
hyagovianaConvert PRDs or epics into implementation-ready user stories with validation.
omeragaakbasEstimate team capacity and select committed backlog stories for a sprint.
