Chaotic Multi-Thread Email Summarizer & Action Item Extractor
Condense a 15+ message tangled email thread into explicit decisions made, open blockers, and single-owner action items.
Compatibility & Specs
Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables3 parameters
Main Prompt Template
163 words • 1112 characters
You are an Executive Operations Analyst and Program Coordinator. I have a long, tangled email thread involving multiple stakeholders with overlapping opinions, partial agreements, and open questions. I need a crystal-clear synthesis.
Full Email Thread Transcript / Text:
[thread_transcript]
Key Stakeholders Involved & Their Roles:
[stakeholders_roles]
Primary Project or Decision in Question:
[primary_project]
Extract and organize a definitive Executive Thread Summary:
1. 2-Sentence TL;DR: What is the current status of the project and the primary consensus reached?
2. Decisions Formally Agreed Upon: Bulleted list of choices that have full consensus, noting who proposed them and who signed off.
3. Open Disagreements & Unresolved Blockers: Exact questions that are still stalling the initiative, categorized by which stakeholder needs to provide the answer.
4. Action Items & Owner Matrix: A clean table with Column 1: Task / Deliverable, Column 2: Single Assigned Owner, Column 3: Agreed Deadline.
5. Draft Consensus Email: A 90-word draft reply to send back to the thread locking in these agreements.
Tip:Variables marked in purple brackets can be tailored below.
Customize Prompt
Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.
Parameters (3)* Indicates required field
[thread_transcript]
The raw text of the back-and-forth emails
[stakeholders_roles]
Names and departments of participants
[primary_project]
What the team was deciding
3 parameters active
Live Customized OutputLive Preview
341 wordsYou are an Executive Operations Analyst and Program Coordinator. I have a long, tangled email thread involving multiple stakeholders with overlapping opinions, partial agreements, and open questions. I need a crystal-clear synthesis.
Full Email Thread Transcript / Text:
Email 1 (Mark - PM): We need to decide if we're launching the redesign on Nov 14 or Nov 21. Marketing wants Nov 14 for the press embargo, but QA says checkout testing needs 3 more days.
Email 2 (Sarah - QA Lead): If we launch Nov 14, mobile safari checkout will only have had 1 round of regression. I vote Nov 21.
Email 3 (Rachel - CMO): Press embargo is already pitched to TechCrunch for Nov 14. Moving it burns credibility with the reporter.
Email 4 (Dave - VP Eng): What if we freeze all code today, have QA focus ONLY on Mobile Safari on Thursday/Friday, and do a soft canary release on Monday Nov 13?
Email 5 (Sarah - QA): That works IF Marketing accepts that any non-critical visual bugs found on Monday won't delay launch.
Email 6 (Rachel - CMO): Agreed, as long as credit card checkout works 100%. Who is notifying the design agency?
Key Stakeholders Involved & Their Roles:
Mark (Lead PM), Sarah (QA Lead), Rachel (CMO), Dave (VP Engineering).
Primary Project or Decision in Question:
Redesign launch date & QA sign-off plan (Nov 14 vs Nov 21).
Extract and organize a definitive Executive Thread Summary:
1. 2-Sentence TL;DR: What is the current status of the project and the primary consensus reached?
2. Decisions Formally Agreed Upon: Bulleted list of choices that have full consensus, noting who proposed them and who signed off.
3. Open Disagreements & Unresolved Blockers: Exact questions that are still stalling the initiative, categorized by which stakeholder needs to provide the answer.
4. Action Items & Owner Matrix: A clean table with Column 1: Task / Deliverable, Column 2: Single Assigned Owner, Column 3: Agreed Deadline.
5. Draft Consensus Email: A 90-word draft reply to send back to the thread locking in these agreements.
How to Use This Prompt
Follow this 3-step workflow to extract high-signal responses from any compatible AI model.
01
1. Tailor the Parameters
Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.
02
2. Send to AI Model
Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.
03
3. Review and Iterate
Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.
Prompt Variables & Parameters
Reference breakdown of every dynamic variable embedded in this prompt template.
| Placeholder | Parameter Name | Type | Status | Description & Guidance |
|---|---|---|---|---|
| [thread_transcript] | Email Thread Transcript | textarea | Required | The raw text of the back-and-forth emailsDefault: Email 1 (Mark - PM): We need to decide if we're launching the redesign on Nov 14 or Nov 21. Marketing wants Nov 14 for the press embargo, but QA says checkout testing needs 3 more days. Email 2 (Sarah - QA Lead): If we launch Nov 14, mobile safari checkout will only have had 1 round of regression. I vote Nov 21. Email 3 (Rachel - CMO): Press embargo is already pitched to TechCrunch for Nov 14. Moving it burns credibility with the reporter. Email 4 (Dave - VP Eng): What if we freeze all code today, have QA focus ONLY on Mobile Safari on Thursday/Friday, and do a soft canary release on Monday Nov 13? Email 5 (Sarah - QA): That works IF Marketing accepts that any non-critical visual bugs found on Monday won't delay launch. Email 6 (Rachel - CMO): Agreed, as long as credit card checkout works 100%. Who is notifying the design agency? |
| [stakeholders_roles] | Stakeholders & Roles | text | Required | Names and departments of participantsDefault: Mark (Lead PM), Sarah (QA Lead), Rachel (CMO), Dave (VP Engineering). |
| [primary_project] | Primary Project / Decision | text | Required | What the team was decidingDefault: Redesign launch date & QA sign-off plan (Nov 14 vs Nov 21). |
Example Execution & Benchmark Output
Sample input arguments and the verified AI response demonstrating expected quality and formatting.
Sample VariablesInputs
[thread_transcript]
Email 1 (Mark - PM): We need to decide if we're launching the redesign on Nov 14 or Nov 21. Marketing wants Nov 14 for the press embargo, but QA says checkout testing needs 3 more days.
Email 2 (Sarah - QA Lead): If we launch Nov 14, mobile safari checkout will only have had 1 round of regression. I vote Nov 21.
Email 3 (Rachel - CMO): Press embargo is already pitched to TechCrunch for Nov 14. Moving it burns credibility with the reporter.
Email 4 (Dave - VP Eng): What if we freeze all code today, have QA focus ONLY on Mobile Safari on Thursday/Friday, and do a soft canary release on Monday Nov 13?
Email 5 (Sarah - QA): That works IF Marketing accepts that any non-critical visual bugs found on Monday won't delay launch.
Email 6 (Rachel - CMO): Agreed, as long as credit card checkout works 100%. Who is notifying the design agency?
[stakeholders_roles]
Mark (Lead PM), Sarah (QA Lead), Rachel (CMO), Dave (VP Engineering).
[primary_project]
Redesign launch date & QA sign-off plan (Nov 14 vs Nov 21).
Expected AI ResponseVerified Result
### Executive Thread Digest
**TL;DR:** The team agreed to maintain the **November 14 public launch** by executing a compromise plan: code freeze begins today, QA focuses exclusively on Mobile Safari checkout testing through Friday, and a soft canary deploy goes live Monday, November 13.
### Decisions Formally Agreed Upon
- Public launch remains Tuesday, November 14 to preserve TechCrunch press embargo.
- Strict code freeze takes effect immediately.
- Marketing explicitly accepts that minor visual/cosmetic bugs will not halt launch, provided credit card processing is 100% verified.
### Open Blockers / Questions
- Ownership of notifying the external design agency regarding the code freeze is unassigned.
### Action Items Matrix
| Deliverable | Single Owner | Deadline |
| :--- | :--- | :--- |
| Execute code freeze and branch cut | Dave (VP Eng) | Today, 5:00 PM |
| Run dedicated Mobile Safari checkout regression suite | Sarah (QA Lead) | Friday, 3:00 PM |
| Deploy 10% canary to production | Dave (VP Eng) | Monday, Nov 13, 9:00 AM |
| Reconfirm embargo with TechCrunch reporter | Rachel (CMO) | Monday, Nov 13, 12:00 PM |
| Notify design agency of freeze schedule | Mark (Lead PM) | Today, 6:00 PM |
Best Use Cases
Scenarios and roles where this prompt produces maximum leverage.
Project managers summarizing complex multi-departmental email deliberations
Executive assistants turning sprawling email chains into actionable leadership briefs
Remote teams establishing clear accountability after asynchronous debates
Tips for Best Results
Techniques to elevate response fidelity
- •Provide a sample paragraph demonstrating your preferred rhythm, cadence, and sentence length.
- •Direct the model to prioritize active voice, clear transitions, and high information density.
- •Have the model generate a rapid outline first before fleshing out long-form copy.
Common Mistakes to Avoid
Frequent failure modes and anti-patterns
- •Accepting the first draft without asking the AI to trim 20% of redundant filler words.
- •Omitting target audience reading level, leading to overly verbose or academic phrasing.
- •Ignoring formatting hierarchy: walls of uninterrupted text perform poorly compared to structured bullet points.
Part of Curated Collections
This prompt is sequenced as part of these goal-oriented workflows
Related AI Prompts
Complementary workflows in Email
Customer Supportbeginner
High-Empathy Customer Support De-escalation Responder
Diffuse furious enterprise customers with radical accountability, immediate remedies, and no robotic apologies.
claudechatgptcopilot
#customer-support#de-escalation#customer-success
Productivitybeginner
Meeting Elimination & Asynchronous Workflow Protocol
Audit recurring team calendar sprawl and author concise asynchronous replacement memos and status updates.
claudechatgpt
#async-work#meeting-reduction#remote-work
Productivityadvanced
Complex Ambiguous Initiative Work Breakdown Structure (WBS)
Deconstruct large, overwhelming projects into chronological milestones, dependencies, and single-owner deliverables.
claudechatgptgemini
#project-management#work-breakdown#wbs