Skip to content
Marketplace

sprint-plan

by phuryn

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Overview

SKILL.mdRead at 8607e3b

Sprint Planning

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Context

You are helping plan a sprint for $ARGUMENTS.

If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

Instructions
  1. Estimate team capacity:
    • Number of team members and their availability (PTO, meetings, on-call)
    • Historical velocity (average story points per sprint from last 3 sprints)
    • Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
    • Calculate available capacity in story points or ideal hours
  2. Review and select stories:
    • Pull from the prioritized backlog (highest priority first)
    • Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
    • Flag stories that need refinement before committing
    • Stop adding stories when capacity is reached
  3. Map dependencies:
    • Identify stories that depend on other stories or external teams
    • Sequence dependent stories appropriately
    • Flag external dependencies and owners
    • Identify the critical path
  4. Identify risks and mitigations:
    • Stories with high uncertainty or complexity
    • External dependencies that could slip
    • Knowledge concentration (only one person can do it)
    • Suggest mitigations for each risk
  5. Create the sprint plan summary:
     Sprint Goal: [One sentence describing what success looks like]
 Duration: [2 weeks / 1 week / etc.]
 Team Capacity: [X story points]
 Committed Stories: [Y story points across Z stories]
 Buffer: [remaining capacity]

 Stories:
 1. [Story title] — [points] — [owner] — [dependencies]
 ...

 Risks:
 - [Risk] → [Mitigation]
  6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.

Think step by step. Save as markdown.

Further Reading

Files 1 file

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add phuryn/pm-skills --skill sprint-plan

More from phuryn

  • create-prdphurynCreate a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.10.4K installs on skills.sh0
  • competitor-analysisphurynAnalyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.3,600 installs on skills.sh0
  • business-modelphurynGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.3,500 installs on skills.sh0
  • privacy-policyphurynDraft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.3,200 installs on skills.sh0
  • brainstorm-ideas-newphurynBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.3,100 installs on skills.sh0
All skills by phuryn