skills.rest
SenzoStack
SenzoStackOFFICIAL
Explore all skills by this author →
GitHub

blocker-radar

Analyze Jira or Linear data and PR activity to surface project blockers.

Updated Mar 30, 2026
Search Tags:#blockers#linear#jira#risk#pull-requests#cycle-time
One-click install
npx skills add https://github.com/SenzoStack/product-delivery-skills --skill blocker-radar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blocker-radar
Source: https://github.com/SenzoStack/product-delivery-skills/tree/main/skills/blocker-radar
Command: npx skills add https://github.com/SenzoStack/product-delivery-skills --skill blocker-radar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blocker Radar helps teams identify blockers, stalled work, and dependency risks early by analyzing tracker data and PR activity to surface actionable insights.

Core Features & Use Cases

  • Detects stale stories, aging PRs, review bottlenecks, and blocked dependencies
  • Flags cycle-time anomalies and cross-repo references
  • Generates a prioritized risk report with recommended actions for sprint planning

Quick Start

Scan my Jira or Linear project for blockers and generate a prioritized risk report.

Frequently Asked Questions about blocker-radar

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

FAQPage Schema
How do I detect blockers and stalled work in a Jira or Linear backlog?▼

To detect blockers in a Jira or Linear backlog, analyze tracker data and PR activity to surface stale stories, aging pull requests, review bottlenecks, and blocked dependencies, generating a structured risk report.

What causes cycle-time anomalies and review bottlenecks in project sprints?▼

Cycle-time anomalies and review bottlenecks in sprints are caused by stale work, aging PRs, and cross-repo references. Analyzing tracker data and PR activity flags these issues early to keep work flowing.

Can I scan both Jira issues and GitHub pull requests for dependency risks?▼

Yes, you can scan both Jira issues and pull requests across repositories. The analysis detects blocked dependencies, cross-repo references, and CI failures to produce a unified prioritized risk report.

What is the best way to surface scope creep and stale stories for sprint planning?▼

The best way to surface scope creep and stale stories is by enforcing a rule set that analyzes tracker data and PR activity, generating a prioritized risk report with recommended actions for sprint planning.

Does this approach work for both Linear cycles and Jira sprints?▼

Yes, this approach is applicable to both Linear cycles and Jira sprints. It analyzes issues and pull requests across these boards to identify bottlenecks, dependency risks, and CI failures consistently.

Related Skills

Explore More Product & Management Skills→
Dev10x-GuruDev10x-Guru
7

Dev10x:gh-pr-create

Automate GitHub pull request creation with ticket extraction and Job Story summaries.

Official
Advanced
Shakes-tzdShakes-tzd
3

strategic-planning

Analyze project graphs to identify bottlenecks, risks, and parallel work.

Community
Intermediate
dyoshikawadyoshikawa
1

prs-awaiting-author

Identify open pull requests requiring author intervention via GitHub CLI.

Community
Intermediate
pcc-labspcc-labs
4

github-org-triage

Analyze open GitHub issues and pull requests to generate prioritization reports.

Official
Intermediate