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]