sprint-status

To get a sprint status snapshot, request a sprint update to scan the current sprint plan and story files. It reads production/sprint-status.yaml or falls back to markdown status inference to summarize progress, days remaining, and completion percentage.

Burndown risk assessment works by comparing agile story completion against time consumed to label the sprint as On Track, At Risk, or Behind. It flags IN PROGRESS stories untouched for 4+ days and escalates risk when stale work is detected.

Yes, you can check sprint progress safely because this is a read-only reporting function. It produces a concise progress snapshot and burndown assessment without proposing file changes, though it includes one clear recommendation when applicable.

No, you do not need a sprint-status.yaml file to track sprint progress. The tool prefers reading production/sprint-status.yaml as the source of truth, but automatically falls back to markdown status inference from story files when the yaml file is absent.

You find stale agile stories by scanning story status markers during an active sprint. The tool specifically flags IN PROGRESS stories that haven't been updated in 4 or more days, escalating risk to highlight work blocking sprint progress.

The best way to assess if your sprint is behind schedule is comparing completion percentage against days remaining. It evaluates your sprint plan and story status to deliver a burndown verdict of On Track, At Risk, or Behind.