kwp-product-management-sprint-planning

Calculate team capacity and organize backlog items into prioritized delivery tiers.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-product-management-sprint-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwp-product-management-sprint-planning
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/product-management/sprint-planning
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-product-management-sprint-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manual sprint planning by centralizing capacity estimation, backlog prioritization, and goal setting into a single, structured workflow.

Core Features & Use Cases

  • Capacity Management: Automatically accounts for team availability, including PTO and recurring meetings.
  • Backlog Prioritization: Helps categorize tasks into P0, P1, and stretch goals to ensure focus.
  • Use Case: Use this during your bi-weekly planning session to quickly generate a balanced sprint plan that accounts for team constraints and project dependencies.

Quick Start

Ask the agent to plan a two-week sprint for your team using the current backlog and accounting for upcoming holidays.

Frequently Asked Questions about kwp-product-management-sprint-planning

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

FAQPage Schema
How do I calculate team capacity for sprint planning while accounting for PTO and meetings?

Sprint planning calculates team capacity by centralizing availability data and automatically deducting time for recurring meetings and PTO. This ensures your capacity estimation accurately reflects actual working hours and team constraints before assigning backlog items.

How do I prioritize a product backlog into delivery tiers for an upcoming sprint?

Backlog prioritization organizes items into structured delivery tiers like P0, P1, and stretch goals. This categorization ensures your team focuses on critical tasks first while maintaining a balanced and achievable sprint scope.

What is the best way to map project dependencies when creating a sprint schedule?

Mapping project dependencies during sprint creation involves integrating project tracking tools to provide accurate, data-driven schedules. This identifies blocking issues early and aligns dependency mapping with your defined sprint goals.

Can I integrate project tracking and calendar tools to generate automated sprint plans?

Generating automated sprint plans requires integration with project tracking and calendar tools. This connection pulls real-time data on availability and backlog status to produce accurate, data-driven sprint schedules without manual friction.

Does this sprint planning approach work for bi-weekly agile cycles and holiday constraints?

This sprint planning approach supports bi-weekly agile cycles by adjusting capacity calculations for upcoming holidays and team availability. It quickly generates a balanced sprint plan that accounts for specific project dependencies and time constraints.

Why does manual sprint planning fail to account for team constraints and backlog priorities?

Manual sprint planning fails because it lacks centralized capacity estimation and automated backlog prioritization. Without structuring tasks into delivery tiers and integrating tracking tools, it cannot accurately account for dynamic team constraints and project dependencies.