risk-escalation

Name: risk-escalation
Author: Productfculty-aipm

70stars33forks

How to install risk-escalation?

productfculty-aipm/pm-copilot-by-product-faculty/risk-escalation

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill risk-escalation

Installs into the current project.

Summary

Use this skill when the user asks to "escalate a risk", "write a risk escalation", "how do I tell leadership about this problem", "write a blocker update", "how do I escalate this issue", "draft a message about this risk", "communicate this blocker", or needs to surface a signifi

Files · 1

View on GitHub

SKILL.md

1	# Risk Escalation
2
3	You are helping the user communicate a risk or blocker to leadership in a way that is clear, calm, and action-oriented. The goal is not to inform — it's to drive a specific decision or action that resolves the risk.
4
5	Framework: Pyramid Principle (bottom-line up front), Lenny's 14 PM habits (always have a POV, but loosely held), SCR framework.
6
7	Key principle: Never escalate a problem without a recommendation. Leadership trusts PMs who bring problems with proposed solutions, not just problems.
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for: the stakeholder being escalated to (their communication style, sensitivities, decision-making style), product context, and any existing tracked risks related to this escalation.
12
13	## Step 2 — Escalation Diagnosis
14
15	Before writing, clarify the situation:
16
17	What is the risk or blocker? (Specific, not vague — "the auth dependency won't be ready until [date]" not "there's a risk")
18
19	What is the impact if this isn't resolved? (Timeline slip? Metric miss? Customer commitment broken?)
20
21	What needs to happen for this to be resolved? (A decision? A resource? An unblocking action from a specific person?)
22
23	What are the options? (At least 2 options — including "do nothing" if that's a realistic option)
24
25	What is the recommendation? (PM's preferred option and reasoning)
26
27	When does a decision need to be made? (Be specific — if the deadline is soft, say so)
28
29	## Step 3 — Write the Escalation
30
31	Use the SCR structure, calibrated for urgency:
32
33	For high urgency (decision needed in < 48 hours):
34	- Format: Slack DM or short email
35	- Open with: "Quick escalation needed — [one sentence on what's at stake]"
36	- Include: situation, ask, timeline, 2–3 options, recommendation
37	- Close with: "Can we sync [today / tomorrow] to align on this?"
38
39	For medium urgency (decision needed in < 1 week):
40	- Format: Email or async doc
41	- Open with: the recommendation (not the problem)
42	- Include: full SCR, options table, recommendation with rationale
43	- Close with: "I'd like to know your thinking on this by [date]"
44
45	For low urgency (FYI / heads up):
46	- Format: Weekly digest mention or async note
47	- One paragraph: what the risk is, how you're mitigating it, what would trigger a more urgent escalation
48
49	## Step 4 — Options Table
50
51	For medium/high urgency escalations, produce a clear options table:
52
53	\| Option \| Description \| Pros \| Cons \| Recommendation \|
54	\|---\|---\|---\|---\|---\|
55	\| Option A \| [e.g., Delay launch 2 weeks] \| [Pros] \| [Cons] \| [Yes/No] \|
56	\| Option B \| [e.g., Launch with reduced scope] \| [Pros] \| [Cons] \| [Preferred — why] \|
57	\| Option C \| [e.g., Do nothing, accept the risk] \| [Pros] \| [Cons] \| [No — why] \|
58
59	Always include "do nothing" as an option, even if to show why it's inadvisable.
60
61	## Step 5 — Calibrate for the Recipient
62
63	From memory, apply the stakeholder's known preferences:
64	- If they're detail-averse: lead with the recommendation and offer details on request
65	- If they're data-driven: lead with the metric impact
66	- If they tend to escalate further: acknowledge that they might want to loop in [person] and give them the context to do so
67
68	## Step 6 — Output
69
70	Produce:
71	- The escalation message in the appropriate format
72	- Options table (for medium/high urgency)
73	- A suggested update to add this risk to `memory/user-profile.md` as a tracked risk

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Risk Escalation

You are helping the user communicate a risk or blocker to leadership in a way that is clear, calm, and action-oriented. The goal is not to inform — it's to driv

Framework: Pyramid Principle (bottom-line up front), Lenny's 14 PM habits (always have a POV, but loosely held), SCR framework.

Key principle: Never escalate a problem without a recommendation. Leadership trusts PMs who bring problems with proposed solutions, not just problems.

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryPlanning

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

risk-escalation

70stars33forks

View on GitHub

How to install risk-escalation?

productfculty-aipm/pm-copilot-by-product-faculty/risk-escalation

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill risk-escalation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Risk Escalation
2
3	You are helping the user communicate a risk or blocker to leadership in a way that is clear, calm, and action-oriented. The goal is not to inform — it's to drive a specific decision or action that resolves the risk.
4
5	Framework: Pyramid Principle (bottom-line up front), Lenny's 14 PM habits (always have a POV, but loosely held), SCR framework.
6
7	Key principle: Never escalate a problem without a recommendation. Leadership trusts PMs who bring problems with proposed solutions, not just problems.
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for: the stakeholder being escalated to (their communication style, sensitivities, decision-making style), product context, and any existing tracked risks related to this escalation.
12
13	## Step 2 — Escalation Diagnosis
14
15	Before writing, clarify the situation:
16
17	What is the risk or blocker? (Specific, not vague — "the auth dependency won't be ready until [date]" not "there's a risk")
18
19	What is the impact if this isn't resolved? (Timeline slip? Metric miss? Customer commitment broken?)
20
21	What needs to happen for this to be resolved? (A decision? A resource? An unblocking action from a specific person?)
22
23	What are the options? (At least 2 options — including "do nothing" if that's a realistic option)
24
25	What is the recommendation? (PM's preferred option and reasoning)
26
27	When does a decision need to be made? (Be specific — if the deadline is soft, say so)
28
29	## Step 3 — Write the Escalation
30
31	Use the SCR structure, calibrated for urgency:
32
33	For high urgency (decision needed in < 48 hours):
34	- Format: Slack DM or short email
35	- Open with: "Quick escalation needed — [one sentence on what's at stake]"
36	- Include: situation, ask, timeline, 2–3 options, recommendation
37	- Close with: "Can we sync [today / tomorrow] to align on this?"
38
39	For medium urgency (decision needed in < 1 week):
40	- Format: Email or async doc
41	- Open with: the recommendation (not the problem)
42	- Include: full SCR, options table, recommendation with rationale
43	- Close with: "I'd like to know your thinking on this by [date]"
44
45	For low urgency (FYI / heads up):
46	- Format: Weekly digest mention or async note
47	- One paragraph: what the risk is, how you're mitigating it, what would trigger a more urgent escalation
48
49	## Step 4 — Options Table
50
51	For medium/high urgency escalations, produce a clear options table:
52
53	\| Option \| Description \| Pros \| Cons \| Recommendation \|
54	\|---\|---\|---\|---\|---\|
55	\| Option A \| [e.g., Delay launch 2 weeks] \| [Pros] \| [Cons] \| [Yes/No] \|
56	\| Option B \| [e.g., Launch with reduced scope] \| [Pros] \| [Cons] \| [Preferred — why] \|
57	\| Option C \| [e.g., Do nothing, accept the risk] \| [Pros] \| [Cons] \| [No — why] \|
58
59	Always include "do nothing" as an option, even if to show why it's inadvisable.
60
61	## Step 5 — Calibrate for the Recipient
62
63	From memory, apply the stakeholder's known preferences:
64	- If they're detail-averse: lead with the recommendation and offer details on request
65	- If they're data-driven: lead with the metric impact
66	- If they tend to escalate further: acknowledge that they might want to loop in [person] and give them the context to do so
67
68	## Step 6 — Output
69
70	Produce:
71	- The escalation message in the appropriate format
72	- Options table (for medium/high urgency)
73	- A suggested update to add this risk to `memory/user-profile.md` as a tracked risk

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Risk Escalation

You are helping the user communicate a risk or blocker to leadership in a way that is clear, calm, and action-oriented. The goal is not to inform — it's to driv

Framework: Pyramid Principle (bottom-line up front), Lenny's 14 PM habits (always have a POV, but loosely held), SCR framework.

Key principle: Never escalate a problem without a recommendation. Leadership trusts PMs who bring problems with proposed solutions, not just problems.

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryPlanning

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type