Sprint Planning

VerifiedSafe

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.

Sby Skills Guide Bot
ProductivityIntermediate
208/30/2026
Claude CodeCursorWindsurfCopilotCodex
#sprint-planning#agile#capacity-estimation#dependency-mapping#risk-identification

Recommended for

Our review

Sprint planning assistant that guides estimation of team capacity, selection of backlog stories, dependency mapping, and risk identification, then produces a structured sprint plan summary.

Strengths

  • Step-by-step structured approach covering capacity, dependencies, and risks.
  • Generates a concrete sprint goal and clear summary.
  • Uses historical velocity and a buffer to set realistic commitments.
  • Highlights critical path and knowledge concentration issues.

Limitations

  • Heavily relies on user-provided data; without it, assumptions are generic.
  • Does not integrate with project management tools like Jira or Trello.
  • The plan is only as good as the backlog quality and availability info supplied.
When to use it

When preparing for a sprint planning ceremony and you need to build a realistic, risk-aware sprint backlog from existing team data and backlog.

When not to use it

When you need to actually update tickets in a project management tool, or when no backlog or availability data exists to base the plan on.

Security analysis

Safe
Quality score88/100

The skill only describes a sprint planning process and does not instruct any execution of commands, file modification, network access, or handling of sensitive data. The only file interaction suggested is reading user-provided backlog or velocity files, which is benign.

No concerns found

Examples

Plan sprint from backlog CSV
Plan the next 2-week sprint for our team of 5 developers using the attached backlog.csv and our velocity data from the last 3 sprints. Provide capacity, story selection, dependencies, and risks.
Capacity with PTO
Help me prepare for sprint planning: estimate our team capacity given two teammates are on PTO next week and our average velocity is 30 story points. Reserve a 15% buffer.
Create sprint plan from Jira export
Create a sprint plan from this Jira backlog export: select stories for the upcoming sprint, map dependencies, identify risks, and propose a sprint goal.

name: sprint-plan description: "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."

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

Related skills