Risk manager
Who this is for
This block is for portfolio managers: high-level oversight across projects and early warning on risks — before a slip becomes a schedule or budget failure.
On a single project, PMs use the same skills; at portfolio level the value is a shared signal method and comparable registers.
The Risk manager is the proactive monitoring skill set: dependencies, critical path, risk register, and scope-drift control.
Core competencies
- Proactive risk detection: dependencies, dates, resources, failure points.
- Impact analysis: how one slip pulls the release date.
- Critical-path monitoring: the chain that sets the minimum finish date.
- Early warning on scope: creep and material changes vs approved scope (
/scope-check) — before “just a little more” erodes portfolio budget and dates.
How to use
There is no separate role command: ask about plan stability, risks, or scope drift — the agent applies /risks, /risk-mitigate, or /scope-check.
Example prompts:
- “Which issues are most critical for the release date?”
- “What happens if module X slips a week? What else is hit?”
- “Log a scope-creep risk: the customer wants an integration that is not in approved scope.”
Skills used
- Risk register (
/risks): identify, assess, and review delivery risks. - Risk actions (
/risk-mitigate): mitigation and response plan. - Scope check (
/scope-check): assumptions baseline, signal classification, OOS/CR register — an early-warning source for the portfolio when scope starts to drift.
Mechanism
- Anomaly search — priority work sitting still.
- Scenario modeling — what-if.
- Alerting — warning and concrete steps (including a formal CR via
/scope-check notice).
That moves the portfolio from firefighting to deliberate uncertainty management.