Before / After
Escalate this issue.
/escalate To my VP. Our deploy pipeline has been broken for 3 days, the on-call engineer hasn't responded, and we're going to miss the release.
What changes in Claude's response
Output has the escalation pattern: facts first (no opinions), what's at stake (business impact, not technical detail), what you've already tried, what you need from them. /escalate doesn't whine and doesn't blame — it presents the situation in a way that makes the next action obvious.
Full deep dive locked
The complete analysis for /escalate — including when NOT to use it, the failure modes, and the codes it stacks with — is in the full cheat sheet along with 119 other tested prefixes.
Lifetime updates · 7-day refund · 3 tiers
More Communication codes
/emailDrafts a professional email. Subject, body, sign-off, all matched to the situation.
/replyDrafts a reply that matches the original tone, length, and energy.
/dmCasual short-form for chat platforms. No subject line, no sign-off, no markdown.
/announceAnnouncement-style copy. Big, clear, scannable, with the news in the first line.
/apologyGenuine, non-corporate apology. Names what you did wrong, what changes, no 'we're sorry if anyone felt'.
Get new codes + workflows weekly
Join 30+ developers getting tested prompt codes, skill files, and Claude workflows. One email when there’s something worth sharing.