sprint-status

# Sprint Status This is a fast situational awareness check, not a sprint review. It reads the current sprint plan and story files, scans for status markers, and produces a concise snapshot in under 30 lines. For detailed sprint management, use `/sprint-plan update` or `/milestone-review`. **This skill is read-only.** It never proposes changes, never asks to write files, and makes at most one concrete recommendation. --- ## 1. Find the Sprint **Argument:** `$ARGUMENTS[0]` (blank = use current sprint) - If an argument is given (e.g., `/sprint-status 3`), search `production/sprints/` for a file matching `sprint-03.md`, `sprint-3.md`, or similar. Report which file was found. - If no argument is given, find the most recently modified file in `production/sprints/` and treat it as the current sprint. - If `production/sprints/` does not exist or is empty, report: "No sprint files found. Start a sprint with `/sprint-plan new`." Then stop. Read the sprint file in full. Extract: - Sprint number and goal - Start date and end date - All story or task entries with their priority (Must Have / Should Have / Nice to Have), owner, and estimate --- ## 2. Calculate Days Remaining Using today's date and the sprint end date from the sprint file, calculate: - Total sprint days (end minus start) - Days elapsed - Days remaining - Percentage of time consumed If the sprint file does not include explicit dates, note "Sprint dates not found — burndown assessment skipped." --- ## 3....