AutoGineer
Generated banner for Sprint Plan
Generated logo for Sprint Plan

Sprint Plan

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Workflow
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The sprint-plan skill provides a systematic approach to sprint planning, ensuring teams balance their workload against historical velocity and available capacity. It guides users through estimating team availability, selecting prioritized stories that meet the Definition of Ready, identifying critical dependencies, and documenting potential risks. The output is a consolidated sprint plan summary that includes a clear sprint goal, capacity metrics, and a risk mitigation strategy.

What it does

  • Calculates team capacity based on availability and historical velocity.
  • Applies a standard buffer to account for unexpected work and technical debt.
  • Selects and sequences stories from a prioritized backlog.
  • Maps internal and external dependencies to identify the critical path.
  • Identifies project risks and suggests actionable mitigation strategies.
  • Generates a structured markdown summary of the sprint plan.

When to use it

  • During recurring sprint planning sessions.
  • When estimating team capacity for upcoming development cycles.
  • When selecting stories from a backlog to balance scope against velocity.
  • When identifying potential blockers or risks before starting a sprint.

Advantages

  • Ensures sprint commitments are grounded in data and historical performance.
  • Promotes proactive risk management and dependency tracking.
  • Standardizes the sprint planning process across the team.
  • Helps maintain a healthy balance between new features and technical debt.

Usage examples

“Help me plan our next 2-week sprint based on the attached backlog and team velocity report.”
The agent analyzes the provided files, calculates the team's capacity, selects the top-priority stories, maps dependencies, and outputs a formatted sprint plan summary.
“Create a sprint plan for our upcoming cycle, accounting for two team members being on PTO.”
The agent adjusts the total capacity calculation to reflect the reduced team size and generates a plan that fits the remaining available story points.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/phuryn/sprint-plan/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip sprint-plan.zip -d .agents/skills

Documentation by Pawel Huryn

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

SKILL.md

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

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/sprint-plan · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download sprint-plan.zip