escalation-tree
Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.
npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Escalation Tree Skill Escalation goes wrong two ways: things sit too long before someone senior is pulled in, or everything gets escalated and senior people drown. A clear escalation tree fixes both — it defines the tiers, the *severity* that sets the path, the *time triggers* that force escalation, and who owns each step. This skill designs that, so the right person is on the right issue at the right time. ## Required Inputs Ask for these only if they aren't already provided: - **The context** — customer support, incident/on-call, or both. - **The tiers/teams** available — tier-1/2/3, engineering on-call, management, exec. - **Severity meaning** — what counts as critical vs. high vs. normal in your context. - **Constraints** — hours of coverage, SLAs/contractual response times, key roles. ## Output Format ### Escalation Tree: [support / incident] **1. Severity levels** — define each (SEV1/P1 … or Critical/High/Normal/Low) with concrete criteria — *what qualifies*, blast radius, and the **response & resolution targets** per level. Ambiguous severity is why escalation fails. **2. The tiers** — who owns what: | Tier | Owns | Can resolve | Escalates when | |---|---|---|---| | Tier 1
- Required Inputs
- Output Format
- Escalation Tree: [support / incident]
- Quality Checks
- Anti-Patterns
- Based On
What does the escalation-tree skill do?
Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.