release-health-analysis

Release health analysis transforms Jira epics, issues, and capacity signals into a quantified risk assessment. It evaluates schedule, staffing, refinement quality, and blocked signals to label features as Critical, At Risk, On Track, or Complete.

Roll up Jira hierarchy data by aggregating progress from Features to Epics to Issues. This computes completion percentages, remaining story points, and capacity risk against sprint and roster capacity for release health tracking.

Reassess refinement coverage by re-checking whether Jira epics sufficiently cover the described work. This determines whether refinement appears complete even when spikes are missing, ensuring accurate release health evaluation.

Yes, Jira MCP search access is required to fetch and roll up Jira hierarchy data. The analysis also requires deterministic file reads and writes in the provided work directory to output the structured analysis.md report.

Refinement reassessment re-checks whether epics sufficiently cover described work, determining completion even when spikes are missing. If epic coverage is insufficient, the assessment will flag incomplete refinement despite closed epics.