AI writes the first draft, you write the final one

Write a draft reply to this email. I'll still be editing the
reply, so I want a draft, not a final version.

INCOMING MESSAGE:
[paste the email text]

WHO I'M REPLYING TO: [relationship — e.g. a client I've
worked with for three years; formal tone]
WHAT I WANT TO HAPPEN: [the outcome for the recipient, not
the topic]
FACTS THAT MUST BE INCLUDED: [dates, numbers, terms — only
what's actually true]
WHAT MUST NOT BE INCLUDED: [what not to promise, not to
admit, not to touch]
TONE: [e.g. matter-of-fact and warm, no apologetic openers]
LENGTH: [max 6 sentences]

Rules:
- don't make up dates, prices, or circumstances; if something
  is missing, write TO ADD: [what] at the end
- don't open with phrases like “thank you for your email” or
  “hope you're doing well”
- no closing offers like “please don't hesitate to reach out
  with any questions” unless I explicitly ask for one
- suggest a subject line too, if it should change

For this situation, write three versions of a reply, not one:

SITUATION: [description]
INCOMING MESSAGE: [paste it]
WHAT I WANT: [outcome]

A) SOFT — maximally accommodating, protects the relationship,
   gives ground on [what's negotiable]
B) NEUTRAL — matter-of-fact, no emotion, just facts and the
   next step
C) FIRM — clearly holds my position, polite, but leaves no
   room for negotiation

For each version, add one sentence on what I risk by sending
it, and how the recipient is likely to react.
All three max 8 sentences. Don't mark any of them as
recommended.

Write a rejection of this request.

REQUEST: [paste the message]
WHO: [relationship]
REAL REASON FOR THE REJECTION: [the actual reason]
WHAT I CAN SAY OUT LOUD ABOUT THE REASON: [what's shareable —
leave the rest unwritten]
ALTERNATIVE I'M OFFERING: [or “none”]

Structure:
1. One sentence acknowledging I understand the request — no
   flattery.
2. A clear no in the second or third sentence. Not “that will
   unfortunately be complicated,” an actual rejection.
3. One sentence with the reason. Not one extra apology.
4. An alternative, if one exists, as a concrete offer with a
   date.

Max 6 sentences. Don't use the conditional where it's actually
a decision (“we wouldn't be able to” → “we won't”).
Don't open with an apology.

Write a follow-up. They haven't replied and I need to move
this forward.

WHAT HAPPENED: [what I sent, when, what was agreed]
WHICH FOLLOW-UP IS THIS: [first / second / last before
escalating]
IMPACT OF THE DELAY: [what specifically gets held up or
costs more]
WHAT I NEED: [a reply / delivery / a signature] BY [date]
RELATIONSHIP: [relationship and how much I can push]

Rules:
- don't assume or imply bad intent
- state facts and dates exactly as I gave them above, don't
  do any math
- no passive-aggressive phrasing (“as I mentioned before,”
  “once again,” “still waiting”)
- end with one specific request with a date, not an
  open-ended ask
- for the second follow-up and beyond, add a sentence on what
  happens if no reply arrives — matter-of-fact, not a threat

Max 5 sentences. Suggest a subject line that makes the
point clear without opening the email.

Write an escalation email. I need to move this up because it
hasn't budged at my level.

PROBLEM: [what specifically isn't working — facts, not
impressions]
WHAT I'VE ALREADY TRIED: [steps and dates]
IMPACT: [on the deadline, the budget, the client, the risk]
WHO I'M WRITING TO: [role, how far removed from the problem]
WHAT I NEED FROM THEM: [a decision / resources / authority —
specifically]
BY WHEN: [date and why that date]

Rules:
- no evaluation of individuals, no names in the role of
  culprit; describe processes and facts
- the “what I've tried” section has to be verifiable, don't
  pad it
- offer 2 solution options and note what each one requires
- tone: calm, matter-of-fact, no urgency and no drama
- structure: 3 short paragraphs (status / impact / what I
  need) plus bullets with the options

Attach a subject line variant that makes clear this needs a
decision, not just information.

Write an apology email. This happened on our end.

WHAT HAPPENED: [factually, without explaining the
circumstances]
IMPACT ON THE RECIPIENT: [what it cost them — time, money,
extra work]
WHAT WE'RE ALREADY DOING: [concrete steps and who's doing
them]
BY WHEN IT WILL BE FIXED: [date]
FUTURE SAFEGUARD: [what we're changing so this doesn't
happen again]
WHAT I'M NOT OFFERING: [discounts, compensation, or promises
I don't have approval for]

Rules:
- apologize in the first or second sentence, clearly and
  once; don't repeat it
- no “if we caused any inconvenience” — either we did, or we
  didn't
- don't blame circumstances, vendors, or the recipient
- don't offer any compensation beyond the “what I'm not
  offering” section
- end with one concrete next step, not a plea for
  understanding

Max 8 sentences, tone serious and calm, no self-flagellation.

Below is the full email thread. Reply on my behalf to the
last message.

THREAD (oldest at the top):
[paste the whole thread, including From/To/Date headers]

I AM: [your name and role in the thread]
WHAT I WANT FROM THIS REPLY: [outcome]
TONE: [tone]
LENGTH: [sentence count]

Rules I insist on:
- stick to the facts in the thread; don't infer, don't
  generalize
- don't promise anything I haven't already promised in the
  thread
- if messages in the thread contradict each other, flag the
  contradiction and ask what applies — don't decide it for me
- respect what I've already declined; don't reopen it
- take figures (dates, amounts, numbers) verbatim from the
  thread, don't recalculate them

Above the reply, write 3 bullets: what's still open in the
thread, what the recipient wants from me, and what I want
from them.

Don't write a reply yet. Pull the facts out of this thread
for me:

[paste the thread]

1. COMMITMENTS — who promised what to whom, with a date and
   the exact sentence it comes from.
2. DEADLINES — every date mentioned in the thread and what's
   tied to it. Flag which have already passed.
3. NUMBERS — amounts, counts, ranges, including who stated
   them and when.
4. OPEN QUESTIONS — what nobody has answered.
5. CONTRADICTIONS — places where two messages disagree.

Don't calculate or round anything. Where the author of a
claim isn't clear, write UNCLEAR. Don't draw any conclusions.

I'm attaching [8] emails I wrote and sent myself. They're
ordinary work messages, nothing especially polished.

[paste the emails]

Describe my style so it can be used to write an email that
sounds like me:

1. OPENINGS: exactly how I open (quote 3 examples)
2. CLOSINGS: how I close and sign off (quote 3 examples)
3. FORM OF ADDRESS: formal or informal, first names, titles
4. SENTENCES: length, whether I write in bullets or flowing
   prose
5. TYPICAL WORDS: phrases that recur
6. WHAT I NEVER USE: phrasing I clearly avoid
7. DEGREE OF POLITENESS: where I'm terse and where I soften

Work only from the attached emails. Where the sample's too
small for a conclusion, say so instead of stating it as fact.
The output needs to be specific enough to use as an
instruction.

I used this prompt and the result was good:

[paste the prompt]

Turn it into a general-purpose template I'll reuse for the
same type of email:
- replace the variable parts with bracketed placeholders that
  say what goes there (not [text], but [reason for the
  rejection, 1 sentence])
- keep the rules that worked verbatim
- add a line for tone and length so those can vary
- finish with 4 points I should check in the draft before
  sending

The template has to work for a situation you haven't seen.

Here's a draft email I'm about to send:

[paste the draft]

CONTEXT: [who it's going to, what the goal is]

Don't rewrite it. Just list findings in five categories:

1. COMMITMENTS — sentences that commit me to something
   (a deadline, a price, scope, a guarantee). Quote them
   verbatim.
2. TONE — spots that might land sharper or softer than I
   probably intend. Quote and explain why.
3. UNSUPPORTED FACTS — numbers, dates, and facts I haven't
   backed up anywhere in the request.
4. SENSITIVE DATA — personal data, internal information, or
   third-party details that might not belong here.
5. AMBIGUITIES — sentences that can be read two ways.

At the end, write in one sentence how the message will
probably land with a recipient who's having a bad day.

I'm attaching an email I need help replying to. Before that,
make a working version of it:

[paste the email]

- replace people's names with their role ([client], [colleague
  from production])
- replace company names with [other party], [vendor]
- remove phone numbers, addresses, email contacts, contract
  numbers, payment reference numbers, and bank details
- keep amounts only where they're necessary for the reply
- don't otherwise change the content, tone, or structure

Return the cleaned version and a list of what you replaced
below it.