at-risk-detection

Detect at-risk GitHub issues and pull requests from activity, labels, and deadlines.

1|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/britt/llpm --skill at-risk-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: at-risk-detection
Source: https://github.com/britt/llpm/tree/main/skills/at-risk-detection
Command: npx skills add https://github.com/britt/llpm --skill at-risk-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill proactively identifies potential issues and pull requests that are at risk of causing delays or problems in your project, such as stale items, blocked work, or approaching deadlines.

Core Features & Use Cases

  • Stale Item Detection: Flags issues and PRs with no recent activity.
  • Blocker Identification: Detects issues or PRs explicitly marked as blocked or waiting.
  • Deadline Risk Assessment: Warns about upcoming or overdue milestones.
  • Scope Creep Monitoring: Identifies issues with excessive comments or PRs with large changes.
  • Assignment Issues: Highlights high-priority items lacking an assignee.
  • Use Case: Before a sprint planning meeting, use this skill to quickly surface all critical issues that are blocked or have approaching deadlines, allowing the team to address them proactively.

Quick Start

Use the at-risk-detection skill to check the project health for stale issues and upcoming deadlines.

Frequently Asked Questions about at-risk-detection

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

FAQPage Schema
How do I detect stale GitHub issues and blocked pull requests in my project?

You can detect stale GitHub issues and blocked pull requests by analyzing repository activity, labels, and deadlines using the GitHub API. This skill flags items with no recent activity or explicitly marked blockers to highlight project risks.

What is the best way to monitor GitHub project health for approaching deadline risks?

Monitoring GitHub project health for deadline risks involves assessing upcoming or overdue milestones and high-priority items lacking an assignee. This skill analyzes issue data to warn about approaching deadlines and scope creep.

Can I identify scope creep and unassigned high-priority items using GitHub issue comments?

Yes, you can identify scope creep and unassigned high-priority items by retrieving GitHub issues with comments. This skill highlights issues with excessive comments and flags high-priority work that lacks an assignee.

How do I surface blocked work before a sprint planning meeting?

To surface blocked work before sprint planning, you analyze GitHub issues and pull requests for explicit blockers, stale activity, and approaching deadlines. This allows teams to proactively address critical delays.

Does this project risk detection require any specific GitHub repository permissions?

Project risk detection utilizes GitHub API tools like list_github_issues and get_github_issue_with_comments, requiring standard API access to read issues, pull requests, labels, and milestone data.

Why are some GitHub issues flagged as deadline risks when they have recent activity?

GitHub issues are flagged as deadline risks when linked to upcoming or overdue milestones, regardless of recent activity. This skill assesses milestone dates and assignment status to identify potential delays.