Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Agile Sprint Capacity Planner

project manager planning skill risk: low

Agile Sprint Capacity Planner

The prompt asks the model to plan a sprint by estimating team capacity, selecting and sequencing stories from the backlog, mapping dependencies, identifying risks with mitigations,…

SKILL 1 file

SKILL.md
---
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

- [Product Owner vs Product Manager: What's the difference?](https://www.productcompass.pm/p/product-manager-vs-product-owner)

INPUTS

$ARGUMENTS REQUIRED

sprint or team context string

REQUIRED CONTEXT

  • sprint context or $ARGUMENTS describing the team/project

OPTIONAL CONTEXT

  • backlog files
  • velocity data
  • team rosters
  • previous sprint reports

ROLES & RULES

Role assignments

  • You are helping plan a sprint for **$ARGUMENTS**.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Sprint Goal, Duration, Team Capacity, Committed Stories, Buffer, Stories, Risks
Constraints
  • use the exact sprint plan summary template provided
  • include sprint goal, capacity, committed stories, buffer, stories list, and risks sections

SUCCESS CRITERIA

  • Estimate team capacity
  • Review and select stories
  • Map dependencies
  • Identify risks and mitigations
  • Create the sprint plan summary
  • Define the sprint goal

CAVEATS

Dependencies
  • user-provided files (backlogs, velocity data, team rosters, or previous sprint reports)
  • $ARGUMENTS
Missing context
  • Definition of Ready criteria
  • Preferred story point scale or hour conversion
  • Output file name or location
Ambiguities
  • $ARGUMENTS placeholder is undefined in the prompt text
  • How to integrate or reference provided files is not specified beyond 'read them first'

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.88
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Replace $ARGUMENTS with an explicit placeholder such as {{team_or_project}} and document its expected content
  • Add an optional 'Input files' section that describes how file contents should be incorporated into each step

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.