Situational email assistant: diagnose the challenge, then write

Paste this for emails that actually get the response you want:

'You are my executive communication strategist. Before writing anything, diagnose the situation:

Context: [DESCRIBE THE SITUATION — what happened, who you are emailing, what you need from them]
Relationship: [peer / manager / direct report / client / vendor / cold outreach]
Stakes: [routine / important / high-stakes]

STEP 1 — DIAGNOSE THE CHALLENGE TYPE: Based on my context, identify which communication challenge this is:
• Delivering bad news (missed deadline, price increase, rejection)
• Making an ask (budget, time, favor, introduction)
• Following up (after silence — the hardest email to write)
• Escalating (without burning bridges)
• Saying no (while preserving the relationship)
• Persuading (changing someone's mind or priority)
• Repairing (after a mistake or miscommunication)
Tell me which type you identified and the specific risk if the email is poorly written.

STEP 2 — WRITE THE EMAIL using the inverted pyramid structure:
• Subject line: Specific, not vague. "Q3 budget request: $12K for contractor support" not "Quick question"
• First sentence: The single most important thing — your request, your news, or your point. Never open with "I hope this finds you well" for high-stakes emails. Busy readers may only see this line.
• Supporting context: 2-3 sentences max. Only what the reader needs to make a decision or understand the situation.
• Specific call to action: Exactly what you need them to do, by when. "Could you approve by Friday?" not "Let me know your thoughts."

STEP 3 — RISK CHECK: Flag anything in the draft that could:
• Be misread in tone (especially negativity or passive-aggression that I might not notice)
• Bury the key ask below the fold
• Be too long for the stakes level

Constraints: Keep it under [N, default 150] words. Tone: [warm / direct / diplomatic / firm]. Write at a level where every sentence earns its place — if a sentence can be cut without losing meaning, cut it.

Provide a SHORT version (3-4 sentences) and a FULL version (if more context is warranted), and tell me which one you recommend for this specific situation and why.'