Optimizer

Make the prompt do the work

An email, a review, a document, a plan, a chunk of code — anything where you want the work produced.

Your current prompt

**Situation**
You are an experienced professional who must tell a counterparty something they will not want to hear - a missed date, a declined request, a price change, a reversed decision. The relationship continues afterwards, so the message has to be honest without being defensive and brief without being cold.

**Task**
Write the email. State the bad news, own what is ownable, give the reader what they need to replan, and make the next step unambiguous.

**Objective**
1. Cap it at 180 words.
2. Put the news in the first two sentences. No context paragraph before it, no gratitude opener.
3. State the cause in one sentence, in the active voice, with the actor named. If we caused it, say we did.
4. Give the reader the three facts they need to replan: what is now true, by when, and what is unaffected.
5. Offer at most two options, each with its own cost, and a recommendation.
6. Close with the specific next action, its owner, and its date. Never "let me know if you have questions" as the closing line.
7. Supply a subject line under 50 characters that names the topic, not the emotion.

**Knowledge**
Act as a senior account lead. An apology is one sentence and appears once; repeating it transfers your discomfort to the reader. Never use "unfortunately", "as you know", "due to circumstances beyond our control", or the passive voice for anything we did. Do not blame a named individual or another team. Do not promise a recovery date you have not confirmed - an honest "I will confirm by Thursday" outperforms an optimistic date.

Describe your ideal output (optional)

ModeModel

4 blocks · 4 clarifying questions · Auto rotates through the models your plan unlocks, switching every two runs per mode.

⌘ + Enter

Standard frame

What you will get back

01Situation
2–3 sentences. Who is acting, for whom, and under what pressure. State the stakes concretely ("hundreds of emails daily", "risk of capital loss"). May open "You are an experienced <role>…" when the task is communicative.
02Task
1–2 sentences opening on an imperative verb. When the task is an audit or a review, enumerate the sub-areas — 4 to 6 named failure classes.
03Objective
The deliverable spec, as a numbered checklist. Length caps, required components, severity tiers if it is a review, and a "for every X provide Y" rule. Every concrete item from the ideal-output description reappears here.
04Knowledge
Tone constraints, domain conventions, the persona ("Act as a Senior …"), the standards to adhere to (PEP 8, one-stop metadata), and the fail-safes for when the model lacks information.

Plus 4 clarifying questions you can answer to re-run with more facts.