sprint-plan

Generate sprint plans and status reports from milestone, capacity, and production context.

70|42|Updated Mar 27, 2026

Search Tags:#risk-management #sprint-planning #milestone #status-report #capacity-planning #design-readiness

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow ensures that every sprint reflects the current milestone, completed work, and available capacity so planning does not slip into guesswork or stale assumptions.

Core Features & Use Cases

New sprint generation: Builds a sprint plan with goals, capacity, tasks, carryover, risks, and dependencies whenever a fresh milestone is ready.
Sprint updates: Edits the most recent sprint file with task status changes, blocker notes, and update logs while prompting for approvals.
Status reporting: Produces on-demand status snapshots with completion percentages, progress tables, burndown assessments, and emerging risks using milestone, design, and risk register context.
Use Case: When a product team closes a feature milestone, invoke the skill to gather design readiness, production outputs, and risk data before drafting sprint priorities and dependencies.

Quick Start

Ask sprint-plan to generate a new sprint plan aligned with the current milestone using the latest production and design context.

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 plan that aligns with my current milestone and capacity?▼

Generate a sprint plan by reading milestone definitions, previous sprint files, and design backlog tags to draft goals, tasks, and dependencies. It applies capacity planning and risk registers to ensure the new sprint plan aligns with current production context.

Can I update a sprint file inline with task status changes and blocker notes?▼

Update a sprint file inline to edit task statuses, append blocker notes, and maintain update logs. The skill prompts for approvals while modifying the most recent sprint file to reflect current progress accurately.

What is the best way to produce a sprint status report with burndown and risk assessments?▼

Produce a sprint status report by aggregating milestone, design readiness, and risk register data. It delivers formatted status snapshots containing completion percentages, progress tables, burndown assessments, and emerging risks.

Does sprint planning require design readiness and risk register context for every session?▼

Sprint planning requires design readiness and risk register context for every session to prevent guesswork. It reads production outputs and design backlog tags to validate capacity planning and define sprint priorities accurately.

How do I handle carryover tasks and dependencies when drafting a new sprint plan?▼

Handle carryover tasks and dependencies by reading previous sprint files during new sprint generation. The workflow incorporates carryover items, assesses design backlog tags, and maps dependencies against available capacity.

When should I not use automated sprint generation for my product team?▼

Avoid automated sprint generation when a feature milestone is not ready or production context is missing. The workflow relies on defined milestone inputs and design readiness to draft valid sprint files and next-action guidance.