sprint-plan

Calculate team capacity and prioritize stories for sprint planning.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/686f6c61/PSPO-Agent --skill sprint-plan-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/686f6c61/PSPO-Agent/tree/main/skills/sprint-plan
Command: npx skills add https://github.com/686f6c61/PSPO-Agent --skill sprint-plan-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines sprint planning by aligning team capacity with approved stories, ensuring realistic goals and efficient resource allocation.

Core Features & Use Cases

  • Capacity Calculation: Determines team availability based on duration, focus hours, and AI agent productivity factors.
  • Story Estimation & Prioritization: Assists in estimating story effort using t-shirt sizing and prioritizing based on value, risk, and dependencies.
  • Sprint Viability Check: Verifies if the total estimated effort fits within the calculated capacity, suggesting cuts if necessary.
  • Use Case: A Product Owner needs to plan the upcoming sprint. They use this Skill to input approved user stories, get AI-assisted estimations, calculate the team's available hours (factoring in AI efficiency), and determine which stories can be included, automatically suggesting cuts if the sprint is overbooked.

Quick Start

Use the sprint-plan skill to plan the next sprint with the current team and approved stories.

Frequently Asked Questions about sprint-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate team capacity for sprint planning?

Team capacity for sprint planning is calculated by evaluating sprint duration, individual focus hours, and AI agent productivity factors to determine total available working hours for the upcoming cycle.

What is the best way to prioritize user stories based on value and risk?

The best way to prioritize user stories by value and risk is to rank approved tasks against their potential business impact and technical dependencies, ensuring the most critical work is scheduled first within sprint capacity.

Can I estimate story effort automatically using t-shirt sizing?

Yes, you can estimate story effort automatically using t-shirt sizing to categorize user stories, allowing the system to calculate total effort and verify it fits within the calculated team capacity.

How do I check sprint viability when total estimated effort exceeds team capacity?

Sprint viability is checked by comparing total estimated story effort against available team capacity, automatically suggesting scope cuts or adjustments if the planned work overbooks the sprint duration.

Do I need CSV files to plan sprints with team capacity calculations?

You need team CSVs, story files, and configuration settings to integrate with the sprint plan, providing the necessary data inputs to calculate availability and generate a viable sprint scope.