sprint-planning

Plan sprints by scoping work, estimating capacity, and generating structured plans.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill sprint-planning-foundationforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/product-management/skills/sprint-planning
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill sprint-planning-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and organize a sprint by scoping work, estimating team capacity, and producing a clear sprint plan so teams know what to commit to and how to measure success.

Core Features & Use Cases

  • Capacity estimation: Calculate available team capacity accounting for PTO, meetings, and on-call duties.
  • Backlog scoping & prioritization: Classify work into P0/P1/P2, allocate estimates and owners, and identify stretch vs must-ship items.
  • Sprint plan generation: Produce a structured sprint plan including capacity tables, prioritized backlog, risks, definition of done, and key dates; useful for kickoff, mid-sprint checks, and handling carryover.

Quick Start

Use the command /sprint-planning followed by the sprint name or date range and a brief summary of team availability and prioritized backlog to generate a complete sprint plan.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I calculate sprint capacity when team members have PTO and meetings?

Sprint capacity planning accounts for PTO, meetings, and on-call duties to calculate available team hours, ensuring realistic sprint commitments and predictable delivery.

What is the best way to prioritize a backlog for an upcoming sprint?

Backlog prioritization classifies work into P0/P1/P2 categories, allocating estimates and owners to distinguish must-ship items from stretch goals for structured sprint planning.

How do I handle carryover work and dependencies during sprint planning?

Sprint planning handles carryover and dependencies by identifying risks early, rolling over incomplete items, and mapping blocked tasks to produce a structured sprint backlog.

Can I generate a sprint plan that includes a definition of done and key dates?

Sprint plan generation outputs capacity tables, prioritized backlogs, identified risks, key dates, and a definition of done to guide kickoff and mid-sprint progress checks.

Does sprint planning work for sizing a backlog against limited team availability?

Yes, sprint planning sizes the backlog against actual team availability by factoring in PTO and on-call duties, producing capacity tables to match workload with realistic throughput.