From pm-delivery
Generates sprint plans with goals, prioritized backlogs, story point estimates, capacity breakdowns, agendas, and risks from user-provided backlog items.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-deliveryThis skill uses the workspace's default tool permissions.
Transform raw backlog items into a structured, achievable sprint with clear goals, velocity-calibrated scope, and team-ready output.
Plans sprints in Scrum/agile projects: refines backlog items, defines sprint goal, calculates team capacity, selects items, decomposes into tasks, outputs SPRINT-PLAN.md. Use for new sprints or re-planning.
Plans sprints by estimating capacity (PTO/meetings), prioritizing backlog, setting goals, identifying risks, and generating markdown plans. For kickoffs, sizing against availability, P0 decisions, carryover.
Plans sprints by estimating team capacity from velocity and availability, selecting stories from backlog, mapping dependencies, identifying risks, and defining sprint goals. Use for sprint planning, story selection, or capacity balancing.
Share bugs, ideas, or general feedback.
Transform raw backlog items into a structured, achievable sprint with clear goals, velocity-calibrated scope, and team-ready output.
Ask for (if not already provided):
Use this structure:
"This sprint we will [deliver X outcome] so that [user/business benefit], measured by [success indicator]."
Never write sprint goals as task lists. Always outcome-first.
| Complexity | Points | Description |
|---|---|---|
| Trivial | 1 | Clearly understood, no unknowns |
| Small | 2 | Straightforward, minor effort |
| Medium | 3 | Some complexity, clear path |
| Large | 5 | Complex, needs design or research |
| Very Large | 8 | High uncertainty, may need splitting |
| Epic | 13+ | Too large — must be split before sprint |
Flag any item estimated at 8+ and recommend splitting.
Available capacity = (Team size × Sprint days × Focus hours/day) × Availability factor
Focus hours/day: 6 (accounting for meetings, Slack, admin)
Availability factor: 0.7–0.85 depending on holidays/events
Story points to commit = Historical velocity × Availability factor
Sprint Goal:
[Goal statement]
Team Capacity: [X] story points available (based on [Y] team members, [Z]% availability)
Sprint Backlog:
| Priority | Story | Points | Owner | Acceptance Criteria |
|---|---|---|---|---|
| 1 | [Story title] | [N] | [Team member] | [When X then Y] |
Carry-Overs from Previous Sprint:
Risks & Dependencies:
Sprint Planning Agenda: