sprint-plan

Name: sprint-plan
Availability: InStock
Author: dnkrow

Generates sprint plans and status updates from milestone, workload, and capacity inputs.

1|Updated May 15, 2026

Search Tags:#task breakdown #sprint planning #milestone tracking #risk register #capacity management #QA readiness #feasibility gate

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/dnkrow/skill/tree/main/claude-global/sprint-plan
Command: npx skills add https://github.com/dnkrow/skill --skill sprint-plan-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered milestone, backlog, and capacity signals into a concrete sprint plan with tasks, dependencies, risks, and a ready-to-execute definition of done.

Core Features & Use Cases

Generates or updates sprint plans in either new-plan or update mode, based on the latest milestone, previous sprint outcomes, and discovered implementation-ready design documents.
Balances priorities by gate feedback by optionally spawning a producer feasibility gate (PR-SPRINT) and revising task scope when the plan is unrealistic.
Enforces QA-plan readiness by checking for a sprint-specific QA plan and prompting you to run /qa-plan sprint if it is missing.

Quick Start

Generate a lean sprint plan for the upcoming sprint by running: sprint-plan new --review lean.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema

How do I generate an execution-ready sprint plan from real team capacity?▼

Generate a sprint plan by reading production milestones, prior sprint context, and capacity inputs to coordinate an execution-ready backlog. The plan balances priorities by scanning design documents for implementation-ready items and checking the risk register.

How does sprint planning handle feasibility gates and unrealistic task scope?▼

Sprint planning handles feasibility by optionally spawning a producer feasibility gate (PR-SPRINT) and revising task scope when the proposed plan is unrealistic. This ensures the final backlog aligns with actual production constraints.

Can I update an existing sprint plan with newly completed work and milestone changes?▼

Update existing sprints by processing completed work and milestone inputs to generate a status update. The system optionally writes production/sprint-status.yaml and production/sprints/sprint-[N].md after gate decisions.

Do I need a QA plan before finalizing sprint planning?▼

Sprint planning enforces QA readiness by checking for a sprint-specific QA plan. If the plan is missing, you will be prompted to run /qa-plan sprint to ensure testing requirements are defined before execution.

What's the best way to track milestones and risks during sprint planning?▼

Track milestones and risks by reading production milestone contexts and scanning the risk register during plan generation. This produces a concrete sprint plan with tasks, dependencies, risks, and a ready-to-execute definition of done.

How do I use task breakdown to balance priorities against design readiness?▼

Task breakdown balances priorities by scanning design documents for implementation-ready items and matching them against real capacity. It optionally spawns a feasibility gate to revise scope when the task breakdown exceeds available resources.