What problem does it solve?
It turns Jira sprint data into actionable sprint health insights so your team can spot capacity risks, delivery blockers, and churn patterns early.
Core Features & Use Cases
- Mode-based sprint analysis: run capacity (start-of-sprint), mid-sprint (burndown/blockers/goal risk), or retro (delivery summary/churn/goal analysis).
- Jira data pipeline with guardrails: fetches sprints and sprint issues via MCP Jira tools, persists raw responses to files, transforms them into structured JSON, and delegates analysis to specialized sub-agents.
- Rosters and story-point capacity context: applies roster rules and custom field mappings from the Edge-Scrum laws to compute capacity and committed SP.
Use case: Analyze OCPEDGE Sprint health at the end of a sprint to quantify committed story points, compare against capacity targets, and identify churn signals and goal risks for the retro.
Quick Start
Run the sprint-health skill with the mode you want (capacity, mid-sprint, or retro) to generate a dated Sprint Health report for the active or specified sprint.