sprint-health-check

Analyze sprint tickets to generate a centralized sprint health report.

2|Updated Mar 10, 2026

Search Tags:#blockers #reporting #velocity #sprint #burndown #ghost-done

Ready to run

npx skills add https://github.com/yannmenec/delivery-management-skills --skill sprint-health-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-health-check
Source: https://github.com/yannmenec/delivery-management-skills/tree/main/archive/v1/skills/sprint-operations/sprint-health-check
Command: npx skills add https://github.com/yannmenec/delivery-management-skills --skill sprint-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint health tracking is often manual and error-prone, making it hard to spot blockers, trends, and scope changes before they derail a sprint.

Core Features & Use Cases

Stuck-ticket detection: identifies blocked, stale, and silent tickets to surface high-priority risks.
Velocity analysis & trajectory: computes velocity trends across sprints and projects progress against commitments.
Scope-change detection: highlights mid-sprint changes to assess impact on scope and delivery.
Ghost-done detection: reveals work that is effectively complete but not yet shown as done to improve burndown accuracy.

Quick Start

Provide sprint_tickets, sprint_context, and optionally sprint_history to generate a comprehensive sprint health report.

Frequently Asked Questions about sprint-health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect stuck tickets and blockers during an agile sprint?▼

Sprint health analysis detects stuck tickets by identifying blocked, stale, and silent tickets to surface high-priority risks. It processes sprint tickets and context to flag issues before they derail your sprint delivery.

What is ghost-done detection and how does it improve burndown chart accuracy?▼

Ghost-done detection reveals work that is effectively complete but not yet marked as done. By identifying these hidden tickets, it corrects burndown chart inaccuracies and provides a true picture of sprint progress.

Can I generate a RAG status report for stakeholder updates from sprint tickets?▼

Yes, sprint health analysis produces a centralized report and RAG (Red, Amber, Green) status from sprint tickets and context. This automates reporting for sprint reviews, standups, and stakeholder updates.

How do I track mid-sprint scope changes and assess their impact on delivery?▼

Scope-change detection highlights mid-sprint additions or removals to assess their impact on delivery. By analyzing sprint tickets against context, it identifies scope creep and its effect on sprint commitments.

What inputs do I need to run sprint health analysis and generate a burndown report?▼

You need sprint tickets and sprint context as required inputs, with optional sprint history for velocity tracking. Providing these generates a comprehensive health report and RAG status for automated reporting.