skills.rest
WindXRan
WindXRanCOMMUNITY
Explore all skills by this author →
GitHub

sprint-status

Parse sprint plans and story files to report progress and burndown risks.

Updated Apr 4, 2026
Search Tags:#progress tracking#team collaboration#sprint status#risk detection#read-only reporting#story scanning#burndown assessment
One-click install
npx skills add https://github.com/WindXRan/y3td --skill sprint-status-windxran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/WindXRan/y3td --skill sprint-status-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand how a sprint is going by reading the latest sprint plan and story files, then summarizing progress, burndown signals, and risks.

Core Features & Use Cases

  • Sprint discovery & parsing: Locates the current sprint file (or a specified sprint) from production/sprints and extracts goal, schedule, and story/task entries.
  • Status reporting with fallbacks: Uses production/sprint-status.yaml as the authoritative source when available; otherwise infers status by scanning referenced story files for common status markers.
  • Burndown and risk assessment: Computes time-consumed vs completion percentage to label On Track / At Risk / Behind, and escalates when Must-Have items are blocked or when in-progress stories go stale.

Quick Start

Ask how the sprint is going (for example, “/sprint-status 3”) to get a concise table of story statuses plus a burndown verdict and any attention-needed items.

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 from story files?▼

To check sprint progress, the tool locates the current sprint file and parses referenced story files to extract status markers, computing burndown signals and risk levels. It summarizes completion percentage against time consumed to generate a concise situational snapshot.

How does sprint status inference work when there is no yaml file?▼

Sprint status inference works by scanning referenced story files for common status markers as a fallback. When sprint-status.yaml is absent, it deterministically parses story entries to infer current progress and calculate burndown risk based on sprint dates.

Can I use a yaml file to provide authoritative sprint status reporting?▼

Yes, you can use sprint-status.yaml to provide authoritative sprint status reporting. When available, the tool extracts status directly from this yaml file instead of inferring it by scanning story files, ensuring deterministic progress and burndown assessment.

How is burndown risk assessment calculated for a sprint?▼

Burndown risk assessment calculates time consumed versus completion percentage to label sprints as On Track, At Risk, or Behind. It escalates risk when Must-Have items are blocked or when in-progress stories go stale based on sprint dates.

Do I need write access to generate a read-only sprint progress snapshot?▼

No, you do not need write access to generate a read-only sprint progress snapshot. The tool requires only read-only file access to locate and parse sprint plans and associated story files for deterministic status reporting and risk detection.

Related Skills

Explore More Product & Management Skills→
cenconq25cenconq25
39

sprint-status

Summarize sprint progress from sprint plans and story files.

Community
Intermediate
sumilee-pcusumilee-pcu

sprint-status

Analyze sprint progress files and story markers to generate burndown reports.

Community
Intermediate
wsmanwsman
18

sprint-status

Track sprint progress and task status from markdown sprint plan files.

Community
Advanced
petrkohutpetrkohut

bmad-sprint-status

Parse YAML sprint status files to aggregate progress and risks.

Community
Advanced