sprint-status

Generates a read-only sprint progress snapshot with burndown assessment and stale story detection.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill sprint-status-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/sprint-status
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill sprint-status-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During a sprint, teams lose situational awareness when story status is scattered across sprint plans and story files. This Skill reads the current sprint plan and story files, then produces a concise progress snapshot with burndown assessment, stale story flags, and escalation alerts without modifying any files. ## Core Features & Use Cases - Sprint Progress Snapshot: Reads the sprint plan and story files, classifies each story as DONE, IN PROGRESS, BLOCKED, NOT STARTED, or MISSING, and outputs a status table. - Burndown Assessment: Compares completion percentage against time consumed to classify the sprint as On Track, At Risk, or Behind, with escalation when stale stories are detected. - Stale Story Detection: Flags IN PROGRESS stories with no update in more than 4 days and surfaces them in an Attention Needed section. - Use Case: Mid-sprint, a lead asks "how is the sprint going" and receives a status table showing two Must Have stories blocked with 30% of sprint time remaining, plus a critical flag recommending a replan. ## Quick Start Ask the assistant to run a sprint status check on the current sprint and report progress, burndown, and any at-risk stories.

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 without updating the sprint plan?

Run a sprint status check, which is read-only and never modifies files. It scans the sprint plan and story files for status markers like DONE, IN PROGRESS, and BLOCKED, then outputs a concise snapshot with a burndown verdict and at most one recommendation.

How is sprint burndown calculated from story status?

Burndown compares completion percentage (done stories divided by total) against time consumed percentage (days elapsed divided by total sprint days). Completion within 10 points of time consumed is On Track, 10-25 points behind is At Risk, and more than 25 points behind is Behind.

What happens if sprint-status.yaml does not exist?

The check falls back to scanning markdown story files and the sprint plan for status markers such as DONE, COMPLETE, IN PROGRESS, BLOCKED, and NOT STARTED. A warning note is added recommending you generate a sprint-status.yaml for authoritative tracking.

Can I check the status of a specific past sprint?

Yes, pass the sprint number as an argument and the check searches production/sprints/ for a matching file such as sprint-03.md. Without an argument, it uses the most recently modified sprint file as the current sprint.

When is a story flagged as stale during a sprint?

An IN PROGRESS story is flagged STALE when its Last Updated date is more than 4 days old. Any stale story escalates the burndown verdict to at least At Risk, even if the completion percentage otherwise looks healthy.