Plan and manage sprint lifecycle
sprintcommandsetup L1★11,239
phuryn/pm-skills ↗What it does
Plan and manage sprint lifecycle phases
Best for
Teams running 1-2 week sprints who need capacity estimation, story selection, and structured retrospectives in one workflow.
Inputs
- · Sprint duration (1-2 weeks)
- · Team composition with availability
- · Sprint goal or focus area
- · Backlog items to consider
- · Historical velocity data (optional)
- · Sprint feedback or metrics
Outputs
- · Sprint plan with capacity breakdown and story selection
- · Retrospective summary with action items
- · Release notes with user-facing language
Preconditions
- · Team members identified
- · Backlog items prioritized
- · Historical velocity available (optional)
Failure modes
- · Overcommits if velocity data is stale
- · Misses underspecified stories in backlog
- · Release notes may lack marketing appeal without context
Trust signals
- · Three distinct workflow phases (plan/retro/release-notes)
- · Explicit capacity calculation formula (70% of theoretical)
- · Definition of Done checklist included
- · Risk identification step in planning