skills.rest
yannmenec
yannmenecCOMMUNITY
Explore all skills by this author →
GitHub

detect-ghost-done

Detect ghost-done and phantom-progress tickets using PR, release, and deployment signals.

2|Updated Mar 10, 2026
Search Tags:#deployment#jira#velocity#sprint#signal-analysis#ghost-done
One-click install
npx skills add https://github.com/yannmenec/delivery-management-skills --skill detect-ghost-done
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detect-ghost-done
Source: https://github.com/yannmenec/delivery-management-skills/tree/main/archive/v1/skills/sprint-operations/detect-ghost-done
Command: npx skills add https://github.com/yannmenec/delivery-management-skills --skill detect-ghost-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ghost-done and phantom-progress issues inflate WIP and obscure sprint metrics, leading teams to misjudge progress and capacity.

Core Features & Use Cases

  • Ghost-done detection: identifies tickets that are effectively done but not closed using multi-signal evidence (PR merged, fix version released, deployment label).
  • Phantom-progress detection (truth audit): optionally surfaces tickets showing active status without corresponding PR activity when data is available.
  • Actionable guidance: for each flagged item, suggests concrete next steps and calculates velocity/completion impact.

Quick Start

Run the ghost-done detector on your current sprint data and review the flagged tickets to clean your sprint metrics.

Frequently Asked Questions about detect-ghost-done

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

FAQPage Schema
How do I detect ghost-done tickets to clean sprint metrics?▼

Ghost-done issues are tickets effectively done but not closed. This Skill identifies them by evaluating sprint board fields and multi-signal evidence like PR merges, fix versions, and deployment labels against a minimum-signal rule.

How do I find phantom-progress issues on my Jira sprint board?▼

Find phantom-progress issues by auditing sprint board data for tickets showing active status without corresponding PR activity. This workflow optionally surfaces these mismatches when data is available to clarify true WIP.

What signals are required to flag a ticket as ghost-done?▼

Flagging a ticket as ghost-done requires evaluating it against a minimum-signal rule that checks for a merged PR, a released fix version, and a deployment label to confirm completion status.

Can sprint velocity be calculated if PR or deployment signals are missing?▼

Yes, sprint velocity can be calculated even when signals are missing. The workflow computes velocity and completion impact while gracefully degrading when data like PR status or deployment labels are unavailable.

How do I calculate the velocity impact of phantom-progress tickets?▼

Calculate the velocity impact of phantom-progress tickets by running the detector on your current sprint data. It evaluates ticket fields and computes the velocity and completion impact for each flagged item.

Related Skills

Explore More Software Engineering Skills→
cruzanstxcruzanstx
6

prompt-manager

Manage prompt files with CRUD operations and JSON outputs.

Community
Advanced
mahg-esmahg-es
3

velocity

Calculate team velocity metrics from sprint history and generate a velocity report.

Official
Intermediate
EmergenceAIEmergenceAI
2

create-bug

Create structured Jira bug reports with environment and regression analysis.

Official
Advanced
bbakbbak
15

wip-stability-chart

Generate a dark-themed React/Recharts WIP stability chart from analyze_wip_stability output.

Community
Advanced