Our review
Plans a sprint by estimating team capacity, selecting backlog stories, mapping dependencies, and identifying risks, then produces a structured sprint plan summary.
Strengths
- Step-by-step structured approach to sprint planning
- Includes capacity buffering and velocity analysis from historical data
- Explicitly maps dependencies and identifies the critical path
- Outputs a clear, reusable sprint plan template
Limitations
- Requires accurate input data (velocity, availability, backlog quality) to be effective
- Does not automate estimation or replace team discussion
- Focused on story points, less suited to time-based or Kanban teams
Use when preparing for a sprint planning ceremony with a prioritized backlog and historical velocity data.
Do not use for continuous flow/Kanban planning or when the team lacks any backlog or estimation data.
Security analysis
SafeThe skill provides guidance for sprint planning, including reading user-provided files and generating a markdown summary. It does not instruct any execution of shell commands, network calls, file deletion, secret exfiltration, or any destructive/obfuscated actions. No allowed tools are declared, and no unsafe instructions are present.
No concerns found
Examples
Plan our next sprint for a team of 6 developers. We have 3 people out on PTO next week. Use our JIRA backlog and last 3 sprints' velocity from the attached files.Help me plan a 1-week sprint focusing on the payment feature. Here are the backlog items and team availability.Create a sprint plan for our mobile app team. Prioritize bug fixes and the login overhaul. We have velocity data in velocity.csv.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
-
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
-
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
-
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
-
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
-
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] -
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
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.