sprint-plan

Generate sprint backlog files from epics and stories with ownership and velocity considerations.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill sprint-plan-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill sprint-plan-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning is a time-consuming activity that often loses track of epics, stories, and team capacity, leading to misaligned delivery and stalled progress.

Core Features & Use Cases

  • Generates a sprint backlog by translating epics and stories into concrete sprint work with ownership and velocity considerations.
  • Updates in-flight sprints to reflect changes in capacity, milestones, and dependencies.
  • Outputs a shareable sprint plan file at production/sprints/sprint-NNN-<slug>.md to enable team alignment.

Quick Start

Run /sprint-plan new to generate a fresh sprint plan.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I generate a sprint backlog from existing epics and stories?

To generate a sprint backlog, the sprint-plan tool translates your input epics and stories into concrete sprint work, factoring in team velocity and ownership. It outputs a shareable sprint plan file for team alignment.

What is the best way to handle mid-sprint capacity changes and milestone shifts?

Handling mid-sprint capacity changes involves updating your in-flight sprint plan to reflect new milestones and dependencies. This ensures your sprint backlog remains executable and aligned with current team capacity.

Can I use sprint planning outputs for team collaboration and alignment?

Yes, sprint planning outputs a shareable sprint plan file at production/sprints/sprint-NNN-<slug>.md. This file enables team collaboration by providing a concrete, executable sprint backlog with clear ownership.

What input files do I need to plan a new sprint?

Planning a new sprint requires input from production/epics/*, design/concept.md, and production/session-state/active.md. These files provide the necessary epics, stories, and session context to build the sprint backlog.

When should I update an in-flight sprint plan?

You should update an in-flight sprint plan after milestones shift or when mid-sprint corrections are needed across production/epics/* paths. This keeps the sprint backlog aligned with actual capacity and dependencies.