sprint-status

Read sprint plans and story entries to compute burndown data.

Updated Aug 27, 2026

Search Tags:#agile #status #sprint #risk #project-management #burndown

Ready to run

npx skills add https://github.com/nevesb/idol-agency-maker --skill sprint-status-nevesb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill sprint-status-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a quick, readable snapshot of sprint health by reading the current sprint plan, story statuses, and burndown indicators, enabling teams to quickly understand progress and risks.

Core Features & Use Cases

Reads the active sprint plan and associated story entries to extract status and estimates.
Calculates days remaining and progress against the sprint timeline, surfacing risks when needed.
Produces a concise 30-line-or-less report suitable for standups, planning meetings, or executive summaries.

Quick Start

Run /sprint-status with an optional sprint number to generate a concise sprint snapshot.

Frequently Asked Questions about sprint-status

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

FAQPage Schema

How do I check sprint health and burndown status for an active sprint?▼

Sprint health is checked by reading the active sprint plan and story entries to extract statuses and compute burndown data. This provides a concise snapshot of progress and risks for standups or planning.

How do I generate a quick sprint report for daily standups?▼

You can generate a concise sprint report by running the status check on the current sprint plan. It calculates days remaining and progress against the timeline, producing a 30-line-or-less summary suitable for standups.

Can I calculate sprint burndown for a specific sprint number?▼

Yes, you can calculate sprint burndown for a specific sprint by providing an optional sprint number. The tool reads the specified sprint plan and associated story entries to extract estimates and compute progress data.

How does sprint status validation handle missing or stale story entries?▼

Sprint status validation flags missing files and identifies stale work when possible. It validates extracted statuses from story entries to ensure the sprint health assessment accurately reflects current project data.

What is the best way to assess project risk using sprint burndown data?▼

The best way to assess project risk is by calculating days remaining against the sprint timeline and extracting story statuses. This surfaces potential risks and stale work, enabling teams to quickly understand sprint progress.

Do I need a sprint-status.yaml file to track sprint progress?▼

No, a sprint-status.yaml file is optional. The tool primarily uses production sprints data and story entries to compute burndown data, but it will apply configurations from the yaml file when present.