agentsclimarketplace

Escalation

Skill janellecipriano/pm-skills/skills/escalation

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install
npx -y skills add janellecipriano/pm-skills --skill escalation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft a clear, professional, unemotional escalation — the problem, impact, what's been tried, and a specific ask with a deadline. Use when the user says "escalate this", "write an escalation", "I need to raise this to leadership", "we're blocked and need help", or needs to ask for intervention without sounding alarmist or blaming.

SKILL.md

2.0 KB, as published. Nobody here has run it

Escalation

Draft an escalation that gets help fast by being calm, factual, and specific — not a complaint, a request for a decision or unblock.

When to use

  • A blocker, risk, or conflict needs a higher level of authority to resolve.
  • The user needs help framing a hard message constructively.

Principles

  • Facts, not feelings. Describe impact objectively; avoid blame and adjectives.
  • Lead with the ask. The reader should know within two sentences what you need from them.
  • Quantify impact. Tie it to dates, dollars, scope, or risk leadership cares about.
  • Show your work. What you've already tried signals this is a real escalation, not a first resort.
  • Make saying yes easy. Offer options and a recommendation; give a clear deadline.

Process

  1. State the ask up front: what decision/action/resource you need, from whom, by when.
  2. Describe the situation in 2–4 neutral sentences.
  3. Quantify the impact if unresolved (timeline, cost, scope, risk).
  4. Summarize what's been tried and why it wasn't enough.
  5. Offer options with a recommendation.
  6. Pick the right audience and channel and match the tone to the relationship.

Output format

**Subject:** Decision needed by {{date}}: {{one-line ask}}

**Ask:** {{specific request}} from {{name}} by {{date}}.
**Situation:** {{neutral facts}}
**Impact if unresolved:** {{quantified}}
**Tried so far:** {{what + outcome}}
**Options:**
1. {{option}} — {{trade-off}}  ← recommended
2. {{option}} — {{trade-off}}

Keep it short and respectful. Escalation is about the problem, never the person.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.