Steal My Prompt Vol. 38: The Email Thread Extractor

The thread has thirty-seven messages. You still cannot tell what was decided.

Three people weighed in. Two of them agreed on something, or seemed to. Someone asked a question that never got answered, and a deadline got mentioned once and never confirmed. Now it is your turn to reply, and you are scrolling up and down trying to reconstruct what everyone actually committed to.

This is the tax on email as a decision-making tool. Context accumulates; resolution does not. Buried in there somewhere is the decision, tangled up with the proposals that went nowhere and the questions everyone forgot to answer.

Paste the full thread into this prompt and it untangles the mess. It separates what was decided from what is still open, names who owns what, flags where people talked past each other, and drafts the one reply that closes the loop.

You stop scrolling. You start moving.

What You Can Use This For

• A long thread where you cannot tell what was actually agreed versus what was only proposed
• A thread you were added to late and need to catch up on without reading every message
• A cross-functional chain where each team assumed someone else owned the next step
• A thread that went quiet, where you need to send the reply that restarts it
• A project handoff, where the person taking over needs the decisions and open items pulled from the email history
• Meeting prep, where you need to know what the thread already settled so you do not re-litigate it in the room

How to Use It

Step 1. Pick your tool. Claude, ChatGPT, Microsoft Copilot, or Gemini on the free tier. The prompt is model-agnostic.

Step 2. For a long or tangled thread, switch on deeper reasoning where your tool offers it on the free tier. In Claude, turn on "Extended thinking." In Microsoft Copilot, click "Think Deeper." In ChatGPT, the model routes harder requests to its reasoning mode on its own, so add "think carefully through the entire thread before answering" to the top of the prompt. Gemini's free tier does not expose a separate deep-reasoning toggle, so run the prompt as written. Deeper reasoning holds more of the thread in view at once and catches the buried open items.

Step 3. Copy the entire thread, including the full quoted history underneath the top message. The loose ends almost always live in the older replies, not the latest one. If you copy only the most recent message, the prompt cannot find what got dropped.

Step 4. Paste below the marked line in the prompt, set your tone, and run.

Step 5. Read the "Crossed wires" section first. That is where the prompt earns its keep. It catches the place where two people assumed different things and never noticed, which is the misalignment that would have bitten you a week later.

Step 6. Edit the drafted reply so it sounds like you, then send.

Pro tip: Before you send the closing reply, paste it back into the prompt and ask, "What is the most likely way this reply gets ignored or misread?" Fix that one thing before it goes out. The reply that closes a loop is the one nobody can misinterpret.

The Prompt

You are my email thread analyst. I am going to paste a long or messy email thread. Your job is to pull clarity out of it so I know exactly where things stand and what to do next. You are an extractor and a synthesizer, not a commentator.

Tone for the drafted reply: [WARM PROFESSIONAL / DIRECT / FORMAL]

Here is the thread:

[PASTE THE FULL EMAIL THREAD BELOW THIS LINE, INCLUDING THE QUOTED HISTORY]

Work through this in order and label each section.

1. Decided. List only what was genuinely agreed or settled in this thread. If something was proposed but never confirmed, it does not belong here. Quote the names of the people who agreed, exactly as they appear in the thread.

2. Still open. List the questions, proposals, and items that were raised but never resolved. For each, note who raised it and who needs to respond.

3. Owners and actions. List every action item, the person who owns it, and the deadline if one was stated. Where the thread never assigned an owner, mark it "owner unclear."

4. Crossed wires. Flag any place where two people appear to be talking past each other, made conflicting assumptions, or where a direct question was asked and never answered. Be specific about who and what.

5. The closing reply. Draft the single email I should send to move this forward. It should confirm what is decided, name the open items, request or assign owners where they are missing, and ask for the specific responses needed to close the loop. Use the tone I specified above. Keep it concise.

Rules. Do not summarize the thread chronologically. Do not invent owners, dates, or decisions that are not in the text. Where the thread is genuinely ambiguous, say so rather than guessing. Output clean, labeled text I can read and act on, with no preamble.

Transparency and Notes

• Tested on real multi-party threads in Claude. Extraction quality holds up well on the kind of threads that actually pile up at work. For very long chains running to many dozens of messages, split the thread in half, run each half, then combine the open items.
• Privacy: email threads are dense with names, company information, and sometimes confidential data. Scrub or anonymize anything sensitive before pasting into a consumer AI tool. These tools are not confidential workspaces, and they are not HIPAA covered if the thread touches health information.
• The prompt drafts. It does not send. Nothing leaves your hands until you decide it does.
• This is an organizational tool, not legal, HR, or financial advice.