sprint-status

To generate a sprint burndown snapshot, the skill reads sprint plan files and story status markers to compute progress, risks, and burndown. It operates in read-only mode and produces a concise 30-line report without modifying your sprint artifacts.

The best way to get agile sprint health awareness is to aggregate sprint plan data and story statuses into a snapshot. The skill scans owner assignments, priorities, and status markers to identify blockers, stale items, and risks, delivering a compact progress report.

Yes, you can track sprint progress without external inputs. The skill operates entirely in read-only mode by reading existing sprint files and status markers directly from your repository to compute burndown and report findings without requiring external integrations.

No, the sprint status skill does not modify sprint plan files. It operates strictly in read-only mode, scanning markdown or YAML story statuses to determine progress, blockers, and stale items, and only reports findings without writing changes to sprint artifacts.

To identify stale stories and risks in an agile sprint, the skill scans story statuses and owner assignments. It reads status markers from markdown or YAML files to detect stale items, compute burndown, and generate recommended actions.

Before requesting a sprint health snapshot, you need sprint plan files containing goals, dates, and tasks, along with story statuses formatted in markdown or YAML. The skill reads these repository files directly to extract owner assignments, priorities, and status markers.