sprint-status

Name: sprint-status
Availability: InStock
Author: easonlao

Produces a sprint progress snapshot with burndown assessment and stale-story flags.

Updated Apr 25, 2026

Search Tags:#agile #progress tracking #risk assessment #story tracking #burndown #sprint status #markdown scanning

Ready to run

npx skills add https://github.com/easonlao/jiazi-game --skill sprint-status-easonlao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/easonlao/jiazi-game --skill sprint-status-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand how a sprint is progressing and whether delivery is on track without waiting for a full review.

Core Features & Use Cases

Fast situational awareness: Produces a concise status snapshot by reading the current sprint plan and scanning for status markers across story/task entries.
Time-based burndown assessment: Computes days remaining, time consumed, completion percentage, and labels the sprint as On Track, At Risk, or Behind.
Attention escalation: Detects stale in-progress items (including via production/sprint-status.yaml when available) and flags missing story references.

Quick Start

Run the sprint-status skill to see the current sprint goal, days remaining, progress table, and burndown verdict.

Frequently Asked Questions about sprint-status

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

FAQPage Schema

How do I get a quick sprint progress snapshot for agile story tracking?▼

To get a sprint progress snapshot, the skill reads your current sprint plan and scans story files to infer status. It computes burndown metrics and outputs a table-based summary with escalation flags for quick situational awareness.

How does burndown assessment work when checking sprint status?▼

Burndown assessment works by computing days remaining and time consumed against your sprint plan. It then labels the sprint status as On Track, At Risk, or Behind based on the completion percentage and remaining time.

Can I use a YAML file as the source of truth for agile risk assessment?▼

Yes, you can use a YAML file as the source of truth. The skill prefers `production/sprint-status.yaml` when available to detect stale in-progress items and flag missing story references during risk assessment.

How do I detect stale in-progress stories in my sprint markdown files?▼

To detect stale in-progress stories, the skill scans story files on disk for status markers and timestamps. It identifies items that have not progressed and flags them for escalation in the summary output.

Do I need any specific dependencies to track sprint status from markdown?▼

No specific dependencies are required to track sprint status. The skill operates independently by locating your sprint markdown file and scanning story entries directly from disk to generate the progress snapshot.

What is the best way to prepare for a sprint check-in without a full review?▼

The best way to prepare for a sprint check-in is generating a concise progress snapshot. This provides immediate situational awareness by capping the output to a table-based summary with escalation flags and one actionable recommendation.