The support reply that de-escalates without grovelling
Drafts a response to an angry customer that acknowledges the real complaint, commits to something specific, and never apologises for things that aren't your fault.
For the messages you rewrite six times: an angry customer, a request you need to decline, a conversation you've been avoiding, and a critique of someone's work.
A sequenced stack — each prompt is meant to feed the next.
How to use it
The common thread is refusing to soften. Every one of these contains an instruction against the polite default — don't lead with an apology, one reason rather than three, no praise sandwich, no "maybe next quarter" unless you mean it.
That isn't a style preference. Softened messages read as automated or evasive, and both guarantee the thing you actually said doesn't land. Two of these will also tell you that you're wrong — the no prompt asks whether it should be a yes, and the conversation prompt asks whether what you want is reasonable.
The stack
Work top to bottom. Copy a prompt, run it, then carry what you learned into the next.
01 → 04
Drafts a response to an angry customer that acknowledges the real complaint, commits to something specific, and never apologises for things that aren't your fault.
Declines a request clearly, without the apologising, over-explaining, or fake availability that turns a no into a maybe and gets you asked again next week.
Works out what you actually want from it, what the other person is likely protecting, and the first two sentences — the part everyone rehearses badly.
Critiques a screen or flow against stated goals, then argues the opposite position — so you get a real second opinion instead of polite agreement.
Keep going
Six prompts covering what a marketing team actually ships in a week — positioning, the landing page, the deck, the leave-behind one-pager, outreach, and social that isn't about nothing.
The four prompts for the part of job hunting that is actually work: making a résumé match one posting, writing a letter that couldn't be sent to anyone else, and walking in prepared.
For the management work nobody trains you for — giving feedback that lands, cutting scope when the date won't move, and writing the update people actually read.