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.