sprint-plan

Break down epics into sprint tasks with estimates, owners, and dependencies.

13|3|Updated Mar 27, 2026

Search Tags:#planning #agile #estimation #backlog #velocity #sprint #story-points

Ready to run

npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill sprint-plan-heaptracetechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/lead-engineer/sprint-plan
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill sprint-plan-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down large epics into well-scoped sprint tasks with estimates, owners, blockers, and dependencies to enable reliable, incremental delivery.

Core Features & Use Cases

Epics to sprint decomposition: break down large features into vertical, shippable sprint tasks with story points.
Dependency mapping & risk flags: identify blockers early and sequence work to minimize sprint disruption.
Capacity planning & assignment: allocate work across team roles with a realistic buffer and velocity awareness.

Quick Start

Start by converting an epic into a sprint board with task cards, owners, estimates, and blockers.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema

How do I break down epics into actionable sprint tasks?▼

To break down epics into actionable sprint tasks, decompose large features into vertical, shippable units with assigned story points, owners, and mapped dependencies. This transforms broad backlog items into trackable work cards for incremental delivery.

What is the best way to estimate story points for backlog grooming?▼

The best way to estimate story points during backlog grooming is to evaluate task complexity within vertical slices of an epic. This ensures estimates reflect actual effort and align with team velocity for reliable sprint outcomes.

Can I map dependencies and flag risks for cross-functional teams?▼

Yes, you can map dependencies and flag risks for cross-functional teams. By identifying blockers early and sequencing work accordingly, you minimize sprint disruption and ensure smooth feature reorganizations.

How do I plan sprint capacity based on team velocity?▼

Plan sprint capacity by allocating work across team roles using realistic buffers and historical velocity awareness. This ensures assigned story points match actual team capacity for predictable agile delivery.

When should I reorganize features during sprint planning?▼

Reorganize features during sprint planning when large epics need decomposition into well-scoped tasks with clear owners and blockers. This is necessary to enable reliable, incremental delivery across cross-functional teams.