AI Agent Hub
Back to skills
Project Risk Early Warning icon

Project Risk Early Warning

Business Operations Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_70c2f807/project-risk-early-warning.

About this skill

Why risk early warning matters

Project delays rarely appear overnight. They accumulate through small progress gaps, resource contention, and unresolved dependencies. The practical problem is that project signals are often scattered across spreadsheets, meeting notes, and gut feelings. By the time a milestone is missed, the team may already be overloaded or the critical path may already be broken. Project Risk Early Warning targets the active project phase and helps turn “something may go wrong” into a concrete, trackable, and actionable risk list.

How it works

The skill converts project data into structured judgments:

  • Progress variance analysis: compares planned and actual progress to quantify delay;
  • Resource bottleneck detection: finds overloaded people, equipment, or budget nodes;
  • Dependency-chain risk: checks fragile links on the critical path;
  • Historical pattern matching: identifies common delay patterns such as scope creep, technical debt, and communication gaps;
  • Risk-level assessment: ranks items by probability × impact to avoid vague “everything is urgent” reports.

The output is not only a list of risks. Each risk should include a concrete description, trigger condition, observable metric, and a mitigation path classified as mitigate / avoid / accept / transfer. When precise data is unavailable, it can still support qualitative analysis using task slippage, staffing status, and unresolved blockers.

Boundaries and caveats

This skill fits projects longer than one month, cross-team projects, or projects with a clear critical path, and can work as a standing weekly check. It is not intended for financial risk assessment, security vulnerability scanning, insurance calculation, or personal career risk evaluation. If a project is already severely delayed, the focus should shift from early warning to retrospective and scope/time re-planning. Because output quality depends on input data and human judgment remains necessary, the report is best used as a discussion aid rather than a final decision.

Use Cases

  • PMs check milestone status in an Excel tracker and identify lagged tasks to assess launch delay risk.
  • Engineering leads entering integration phase identify interface dependencies, test capacity, and critical-path blockers.
  • Team leads prepare weekly reviews, rank risks by probability and impact, and request mitigation, avoidance, acceptance, or transfer options.
  • Delivery managers spot sustained staffing overload, locate overloaded nodes, and propose resource or priority adjustments.

Best For

  • PMs managing multi-phase delivery who need to anticipate schedule risk before milestones.
  • Cross-team leads who must coordinate engineering, testing, and external resource bottlenecks.
  • Project assistants tracking progress in spreadsheets who want to turn informal concerns into a risk list.
  • Tech managers who need to explain risk levels and response options to leadership.