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

detect-stuck-tickets

Detect blocked, stale, and silent tickets in active sprints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface blocked, stale, and silent tickets in the active sprint to enable proactive intervention and healthier sprint flow.

Core Features & Use Cases

  • Layered detection across four signals (blocked, stale, silent, flagged) to surface urgency.
  • Enrichment with blocker chains, PR status, last activity, and risk scoring.
  • Actionable recommendations to unblock work and prevent sprint derailment.

Quick Start

Provide the active sprint tickets data and run detect-stuck-tickets to produce a prioritized stuck-tickets report.

Frequently Asked Questions about detect-stuck-tickets

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

FAQPage Schema
How do I identify stale and blocked tickets in an active sprint?▼

Detect stuck sprint tickets by scanning active sprint data across four signal layers: blocked, stale, silent, and flagged. This surfaces urgency and enables proactive intervention to maintain healthier sprint flow.

What is the best way to surface sprint blockers before they derail progress?▼

Surface sprint blockers before derailment by enriching active ticket data with blocker chains, PR status, and last activity timestamps. Risk scoring prioritizes issues and generates actionable recommendations to unblock work.

How do I prioritize stuck tickets for daily sprint health checks?▼

Prioritize stuck tickets for daily sprint health checks by applying optional sprint context to urgency scoring. Detection layers enrich ticket data with risk scores and recommended actions, helping teams target critical blockers during standups.

Can I use automated risk analysis for silent tickets during sprint planning?▼

Yes, automated risk analysis supports sprint planning by detecting silent tickets lacking recent activity. It enriches ticket data with risk scoring and generates recommended actions to prevent future sprint stagnation.

Does sprint blocker detection work without additional dependencies or components?▼

Sprint blocker detection operates without external dependencies or components. Supply active sprint ticket data, and the four-layer detection mechanism produces a prioritized stuck-tickets report for blocker reviews.

Related Skills

Explore More Product & Management Skills→
OreStudioOreStudio
25

new-sprint-skill

Update sprint backlog files, version strings, and CI configuration for a new Agile sprint.

Official
Intermediate
zephyrwang6zephyrwang6
333

task-drill

Decompose user tasks into actionable steps with AI and human role assignments.

Community
Basic
thavirak-svaythavirak-svay
1

bmad-sprint-status

Summarize sprint status from sprint-status.yaml and recommend the next workflow action.

Community
Intermediate
zm2231zm2231

standup-bot

Collect team standup updates and generate formatted summary reports.

Community
Advanced