sprint-status

Name: sprint-status
Availability: InStock
Author: Negentropy-Laby

Aggregates sprint plans and story statuses into a concise progress snapshot.

3|Updated Jun 3, 2026

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

Ready to run

npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill sprint-status-negentropy-laby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/sprint-status
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill sprint-status-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly determine sprint health by consolidating plan data and story statuses into a compact progress snapshot.

Core Features & Use Cases

Reads the sprint plan and story files to compute current progress, burndown, and risk signals.
Uses sprint-status.yaml as the authoritative status when present, otherwise fallbacks to markdown parsing of entries.
Produces a concise status summary suitable for quick conversations like "how is the sprint going" or "sprint update".

Quick Start

Run /sprint-status to generate a current 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 progress quickly?▼

Sprint health checks aggregate sprint plans and story statuses into a concise progress snapshot, computing burndown metrics to flag risks like stale or blocked work for current or specified sprints.

What is the best way to detect blocked or stale stories in an agile sprint?▼

Detecting blocked or stale stories involves reading sprint plan data and story files to identify statuses like BLOCKED or NOT STARTED, surfacing these risks automatically when paired with a sprint-status.yaml configuration.

How do I generate a sprint status update for a quick project management conversation?▼

Generating a sprint status update consolidates plan data and story statuses into a compact summary, classifying sprint health as On-Track, At-Risk, or Behind for quick conversations about sprint progress.

Do I need a sprint-status.yaml file to compute sprint burndown metrics?▼

You do not need a sprint-status.yaml file to compute burndown metrics; the system uses it as an authoritative status source when present, otherwise falling back to parsing markdown entries from sprint story files.

Can I analyze sprint risks for a specified sprint instead of the current one?▼

You can analyze sprint risks for a specified sprint by applying the health check to a targeted sprint, reading production sprint data to detect statuses and compute burndown metrics for any selected period.

What sprint statuses are detected when calculating project burndown?▼

Calculating project burndown detects DONE, IN PROGRESS, BLOCKED, and NOT STARTED statuses from sprint story files, using these states to compute progress and flag potential sprint risks.