sprint-planning

Decompose epics into sprint tasks and generate a .context/sprint-plan.md output.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill sprint-planning-hamzapixl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/sprint-planning
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill sprint-planning-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint-planning helps teams decompose epics into sprint-sized work, calibrate velocity, and produce coherent sprint plans that align with delivery timelines.

Core Features & Use Cases

  • Breaks epics into sprint-sized tasks and maps them to branches/PRs
  • Velocity calibration using past sessions or default estimates
  • Sprint assignment respecting dependencies and capacity, with risk buffers
  • Generates a concrete .context/sprint-plan.md output with acceptance criteria for spec-review

Quick Start

Run sprint-planning to produce a sprint plan from your existing /task-plan data and velocity history.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I break down product epics into sprint-sized tasks?

Sprint planning decomposes epics into sprint-sized tasks by sourcing work from existing task-plan data, calibrating velocity, and mapping deliverables to iterations. It generates a structured sprint-plan.md output to guide execution.

What is velocity calibration and how does it work for sprint planning?

Velocity calibration estimates sprint capacity using past session data or default metrics. This ensures sprint assignments respect team capacity and dependencies while including appropriate risk buffers for delivery timelines.

How do I map sprint tasks to git branches and pull requests?

Sprint planning maps decomposed epic tasks directly to branches and PRs during sprint assignment. This mapping is recorded in the generated sprint-plan.md output to maintain traceability between iteration work and code delivery.

Can I use existing task-plan data to generate a sprint plan?

Yes, sprint planning produces a concrete .context/sprint-plan.md output file containing the organized iterations, velocity calibration, and branch mappings. This structured document includes acceptance criteria ready for spec-review.

Does sprint planning account for task dependencies and capacity buffers?

Sprint planning requires existing task-plan data and velocity history as input. It processes these prerequisites to calibrate capacity, assign tasks to iterations, and output a structured sprint-plan.md document.

Do I need velocity history to run sprint planning for my epics?

Sprint planning uses velocity history for capacity calibration but can default to estimates when past data is unavailable. It assigns sprint-sized work respecting dependencies and capacity buffers to align with delivery timelines.