sprint-status

Generate a compact sprint status snapshot by reading the current sprint plan and story entries to surface progress, owners, priorities, and blockers in a concise 30-line output. This read-only summary is ready to share for quick standups or PM updates.

Sprint burndown detection calculates days elapsed and remaining, then flags stale stories using last-updated timestamps and identifies blockers via a status scan or markdown markers. It escalates risks with a note when data is outdated or missing.

Yes, you can run the command with an optional sprint number to generate a progress snapshot for that specific sprint. Without a number, it identifies the current sprint by date and loads all related goals and stories automatically.

Track agile story progress safely using read-only operations that load sprint goals, start and end dates, and story estimates. The tool compiles a status table with per-story status and flags risks without altering any of your existing project files.

No, you do not need a sprint-status.yaml file to detect blockers. The tool performs a status scan from sprint-status.yaml if present, but will automatically fall back to parsing markdown markers to identify blockers and compile the status table.

Sprint progress reports flag stories as risks when last-updated timestamps indicate stale entries or when story data is outdated and missing. The tool adds an escalation note to the compact output to highlight these items for timely intervention.