sprint-status

Compute sprint progress tables and risk flags from plan and story files.

Updated May 13, 2026

Search Tags:#progress tracking #risk assessment #burndown #sprint status #stale task detection #yaml status

Ready to run

npx skills add https://github.com/FrancisVarga/the-dream-machine --skill sprint-status-francisvarga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill sprint-status-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint work can drift without visibility, so teams need a fast, accurate snapshot of progress, burndown posture, and emerging risks.

Core Features & Use Cases

Sprint discovery and parsing: Locates the current sprint (or a specified sprint) and reads its plan and story/task entries.
Status source-of-truth support: Uses production/sprint-status.yaml when present, otherwise infers status from sprint markdown and referenced story files.
Burndown and risk signaling: Calculates completion vs. time consumed, flags On Track/At Risk/Behind, and escalates if Must Haves are blocked/not started.
Stale story detection: Flags IN PROGRESS stories with missing or outdated “Last Updated” timestamps to prompt attention.

Quick Start

Run the sprint-status skill to produce a concise progress snapshot and burndown verdict for the current sprint.

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 progress and burndown status mid-cycle?▼

Sprint progress and burndown status are calculated by reading your sprint plan and story files to compare task completion against time consumed, generating a burndown verdict of On Track, At Risk, or Behind. This provides a fast snapshot for mid-cycle check-ins.

How does stale task detection work for in-progress sprint stories?▼

Stale task detection flags in-progress stories with missing or outdated Last Updated timestamps within the repository's story files. This highlights stalled work that needs attention to prevent sprint burndown risks from escalating unnoticed.

What is a sprint-status.yaml file and do I need it to track sprint risks?▼

A sprint-status.yaml file acts as an optional status source-of-truth for tracking sprint risks, but it is not required. If absent, the skill infers sprint status directly from sprint markdown and referenced story files to calculate burndown posture.

Can I use sprint status tracking for specific sprints or only the current active sprint?▼

You can track sprint status for a specified sprint or the current active sprint. The skill discovers the current sprint by default but can parse a specified sprint plan and associated task entries to generate targeted progress snapshots and risk flags.

When should I escalate sprint risks for blocked Must Have stories?▼

Sprint risks for blocked Must Have stories should be escalated when the burndown assessment flags them as not started or blocked. The skill automatically escalates these critical risk flags in the sprint status snapshot to prompt immediate attention.