Risk Escalation logo

Risk Escalation

Community
Productfculty-aipm
risk-escalation

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 significant risk, blocker, or problem to leadership in a way that drives action rather than panic.

Overview

PublisherProductfculty-aipm
RepositoryPM-Copilot-by-Product-Faculty
Skill namerisk-escalation
Stars
80
Forks
34
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Risk Escalation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/risk-escalation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/risk-escalation .claude/skills/risk-escalation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Risk Escalation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Risk Escalation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Risk Escalation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 drive a specific decision or action that resolves the risk.

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.

Step 1 — Load Context

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.

Step 2 — Escalation Diagnosis

Before writing, clarify the situation:

What is the risk or blocker? (Specific, not vague — "the auth dependency won't be ready until [date]" not "there's a risk")

What is the impact if this isn't resolved? (Timeline slip? Metric miss? Customer commitment broken?)

What needs to happen for this to be resolved? (A decision? A resource? An unblocking action from a specific person?)

What are the options? (At least 2 options — including "do nothing" if that's a realistic option)

What is the recommendation? (PM's preferred option and reasoning)

When does a decision need to be made? (Be specific — if the deadline is soft, say so)

Step 3 — Write the Escalation

Use the SCR structure, calibrated for urgency:

For high urgency (decision needed in < 48 hours):

  • Format: Slack DM or short email
  • Open with: "Quick escalation needed — [one sentence on what's at stake]"
  • Include: situation, ask, timeline, 2–3 options, recommendation
  • Close with: "Can we sync [today / tomorrow] to align on this?"

For medium urgency (decision needed in < 1 week):

  • Format: Email or async doc
  • Open with: the recommendation (not the problem)
  • Include: full SCR, options table, recommendation with rationale
  • Close with: "I'd like to know your thinking on this by [date]"

For low urgency (FYI / heads up):

  • Format: Weekly digest mention or async note
  • One paragraph: what the risk is, how you're mitigating it, what would trigger a more urgent escalation

Step 4 — Options Table

For medium/high urgency escalations, produce a clear options table:

OptionDescriptionProsConsRecommendation
Option A[e.g., Delay launch 2 weeks][Pros][Cons][Yes/No]
Option B[e.g., Launch with reduced scope][Pros][Cons][Preferred — why]
Option C[e.g., Do nothing, accept the risk][Pros][Cons][No — why]

Always include "do nothing" as an option, even if to show why it's inadvisable.

Step 5 — Calibrate for the Recipient

From memory, apply the stakeholder's known preferences:

  • If they're detail-averse: lead with the recommendation and offer details on request
  • If they're data-driven: lead with the metric impact
  • If they tend to escalate further: acknowledge that they might want to loop in [person] and give them the context to do so

Step 6 — Output

Produce:

  • The escalation message in the appropriate format
  • Options table (for medium/high urgency)
  • A suggested update to add this risk to memory/user-profile.md as a tracked risk

Frequently asked questions

What does the Risk Escalation AI skill do?

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 significant risk, blocker, or problem to leadership in a way that drives action rather than panic.

Why use Risk Escalation on TypingMind?

Because you install it once and use it with any model. Risk Escalation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Risk Escalation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/risk-escalation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Risk Escalation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Risk Escalation?

As many as you like. As long as a model supports skills, you can use Risk Escalation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Risk Escalation AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇