Our review
Plans a sprint by estimating team capacity, selecting backlog stories, mapping dependencies, identifying risks, and producing a summary plan.
Strengths
- Structured process with explicit capacity buffer (15-20%) for unexpected work.
- Dependency mapping and critical path identification.
- Produces a clear sprint plan summary with goal, capacity, stories, and risks.
- Checks Definition of Ready to avoid committing to unrefined stories.
Limitations
- Assumes the user provides velocity and backlog data; it does not generate estimates itself.
- Does not handle prioritization from a raw product backlog; relies on already-prioritized input.
- Sprint goal definition is generic and may need human validation.
Use when preparing for a sprint planning session with team capacity, prioritized backlog, and velocity data.
Do not use for roadmap-level planning or when there is no backlog/velocity data to work from.
Security analysis
SafeThe skill only provides instructions for sprint planning and does not involve executing code, accessing files, or using any tools. It operates on user-provided arguments and files if supplied, with no destructive or exfiltrating actions.
No concerns found
Examples
Plan our next sprint. The backlog is in backlog.csv, velocity history is in velocity.csv, and team rosters are in team.md. We have 6 developers and 2 are on PTO next week. Provide a complete sprint plan.I'm about to run sprint planning. Here are the top 15 stories from our backlog and our average velocity is 30 points. Help me select stories, estimate capacity, and identify risks.Create a sprint plan for the current iteration including capacity, committed stories, buffer, and risk mitigations. Use the attached sprint data.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.