督办风险排查 · Risk Supervisor

它解决什么问题

项目里的风险不是突然爆发的,而是没人盯的待办慢慢拖成事故:节点过了没人追、问题发现了没人跟、责任分不清。直接问 AI 排查,常给一堆泛泛的「注意沟通」。

这个技能做什么

先收集待办清单与项目背景,再按「影响 × 发生概率」给每项打风险等级,识别延期隐患与阻塞点;输出督办清单:责任人、截止时间、排查问题与升级路径,高风险项附追问话术。

为什么比裸提示词强

• 分级督办:高中低风险分别对待。
• 责任到人:每项有责任人、截止与升级人。
• 带追问:给出催办话术,不靠吼推进。

典型用例

• 每周例会前排查项目风险点。
• 跨部门待办的交期督办。
• 上线前集中排查阻塞项。

局限

依赖你提供的待办与背景信息;无法自动读取项目工具,涉及人事与合规的风险请由负责人确认。

English · 英文介绍

The problem

The risks in the project do not suddenly erupt, but the to-do items that no one is paying attention to gradually turn into accidents: no one pursues after the node is passed, no one follows the problem when it is discovered, and the responsibilities are unclear. Asking the AI ​​directly for troubleshooting often results in a bunch of general "pay attention to communication."

What it does

First collect the to-do list and project background, and then assign a risk level to each item according to "impact × probability of occurrence" to identify potential delays and blocking points; output a supervision list: responsible person, deadline, troubleshooting and escalation path, and follow-up questioning skills for high-risk items.

Why is it better than naked prompt words?

• Graded supervision: high, medium and low risks are treated separately.
• Responsibility assigned to each person: person responsible for each item, deadline and upgrade person.
• Follow-up questions: Give prompting words and do not rely on yelling to advance.

Typical use cases

• Check project risk points before weekly meetings.
• Supervise the delivery of cross-department pending tasks.
• Focus on troubleshooting blocking items before going online.

Limitations

Relies on the to-do and background information you provide; project tools cannot be automatically read, and risks involving personnel and compliance should be confirmed by the person in charge.