sprint-status

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose situational awareness mid-sprint because story status is scattered across sprint plans, story files, and status YAML files. This Skill reads those sources and produces a concise progress snapshot with burndown assessment, stale story flags, and escalation alerts in under 50 lines. ## Core Features & Use Cases - Sprint Discovery and Parsing: Locates the current or specified sprint file in production/sprints/, extracts goal, dates, priorities, owners, and estimates. - Status Aggregation: Reads sprint-status.yaml as the authoritative source or falls back to scanning markdown story files for DONE, IN PROGRESS, BLOCKED, and NOT STARTED markers. - Burndown and Staleness Analysis: Compares completion percentage against time consumed, flags IN PROGRESS stories untouched for 4+ days, and escalates the verdict to At Risk when stale work is found. - Use Case: A product owner asks "how is the sprint going" mid-week and receives a status table, a burndown verdict, a list of Must Haves at risk, and one concrete recommendation without any files being modified. ## Quick Start Ask the assistant to run a sprint status check on the current sprint and report progress, burndown, and any stories that need attention.

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 from markdown files?

Run the sprint status check, which reads the current sprint plan in production/sprints/ and scans story files for status markers like DONE, IN PROGRESS, and BLOCKED. It outputs a progress table, burndown verdict, and one recommendation without modifying any files.

What is the difference between sprint status and a sprint review?

Sprint status is a fast read-only snapshot for situational awareness during a sprint, kept under 50 lines. A sprint review or retrospective is a deeper end-of-sprint analysis handled by separate milestone-review or retrospective workflows.

Does the sprint status check modify my sprint plan or story files?

No, the check is strictly read-only. It never writes files, never changes story status, and makes at most one recommendation per run. Replanning is delegated to the sprint-plan update workflow.

How is a stale story detected during a sprint?

For each IN PROGRESS story, the check reads the Last Updated date field in the story file and calculates days elapsed. Stories untouched for more than 4 days are flagged STALE, which escalates the burndown verdict to at least At Risk.

What happens if sprint-status.yaml is missing?

The check falls back to scanning markdown story files and the sprint plan for status markers, classifying entries without markers as NOT STARTED. It appends a note recommending you generate the YAML file via sprint-plan update for authoritative tracking.