sprint-status

To get a quick sprint status update, this Skill reads your sprint plan and scans story files using Glob and Grep, producing a concise progress snapshot under 30 lines for instant situational awareness.

Sprint burndown risk assessment compares completed stories against time consumed, flagging items as On Track, At Risk, or Behind, and applies staleness escalation for IN PROGRESS stories that lack recent updates.

You do not need a sprint-status.yaml file to track sprint progress; the Skill prefers it as an authoritative source but falls back to markdown-based status inference with stale-story detection when it is absent.

The best way to check agile project tracking status read-only is by using Glob and Grep scanning plus file reads, ensuring no modifications are made to your sprint plan or story files during the status query.

Yes, you can use grep scanning to detect stale stories during active development; the Skill flags IN PROGRESS items with staleness escalation to provide quick burndown insight from Must Have priorities.

Markdown status inference can produce errors for sprint tracking because it relies on parsing text rather than structured data, which is why the Skill prefers production/sprint-status.yaml as the authoritative source.