prompt teardown.
HomeBlogArchive Subscribe
Home Blog Archive Subscribe
RSS feed Reddit community
guide 8 min read
Home › Blog › Rewrite a dead email & plan a week you can finish

Rewrite a dead email & plan a week you can finish

NewsletterEmailProductivityWorkflows

The Take

Every prompt worth keeping this week works by cutting.

The model was never going to run short on words. Left alone it pads and hedges and fills every box you hand it. The useful prompts don’t ask for more. They methodically state what should be left out.

The viral ones over-promise. One template that swears it covers everything.

Everything is the problem.

Seen This Week

1. The prompt that rewrites your email before you send it

You know the feeling. You finish an email & something nags you. Is the wording right, am I missing something. So you paste it in & tell the model “improve this email.” What comes back is the same email with fancier words.

The problem is you’re too close to it. You wrote it & read it 10 times, so it sounds fine in your head. This prompt makes the model read it cold, the way the person getting it would, then rewrite around that. If the structure is the problem, it rebuilds the whole email, not just the sentences.

Before rewriting this email:

1. Tell me who you think the reader is and what I'm asking them to do. If the ask isn't clear from the email, stop and say so, that's the first thing to fix.

2. List the real ways it falls short of that goal. If it's already close, say that instead of inventing problems.

3. Rewrite it. Restructure freely using my voice, don't just polish sentences.

Email:

Why it works:

You don’t need to tell the model who the reader is. It figures that out on its own, then matches the voice given.

Prompt it with “make it better, this is important, don’t make mistakes” & every email comes back timid & overly formal.

Here, an email to a client you don’t want to lose comes back cautious. The same ask to a contractor who works for you comes back more relaxed. The tone should fit your relationship to the reader.

The prompt also asks for the real ways the email falls short & to say so if it’s already close. The model targets the 1 or 2 things that matter instead of padding a list.

One gap: The rewrite can add reasoning you never gave it. For example, ask it to fix an email about a late payment & it might write in a reason for the delay you never mentioned.

Simple fix: Read the rewrite for anything stated as fact that wasn’t in your original, before you send.

2. The prompt that plans an entire week you can finish

We’ve seen variations of a weekly planner prompt. This one asks when your focus is sharpest, takes your task list & lays the week out in a clean day-by-day table. And it looks great on Monday.

Then a Zoom call runs longer than planned, you spend an hour prepping for the next one & you’re behind for the rest of the week.

I ran it on my own week. 2 problems. It trusts you to remember everything on your plate in one answer & it packs every hour, so one surprise breaks the whole plan.

This version fixes both.

One thing before you run it: the first line depends on where your tasks live.

If your model is connected to your calendar or task manager (Google Calendar, iCal, Asana, ClickUp, whatever you use), name it & let it pull from there. If you’re not connected to anything, do a brain dump first. Something like: “Tell me to dump everything on my plate in my own words, messy is fine. Then read the list back to me so I can catch what I forgot.” I have a fuller brain dump prompt here.

Plan my week.

1. Pull my meetings, tasks, and deadlines from my [calendar / task manager]. Ask me only about what's missing.

2. Ask how I work: when my focus is sharpest, and whether I stay on one task until it's done or switch between tasks. If I stay, keep deep work in as few blocks as possible. If I switch, ask how often and when.

3. Build the week as a day-by-day table. Hardest work in my sharpest hours. Leave a block open each day for a task that runs longer than expected.

4. Name 1 task I should drop this week, and why. If everything fits, say so.

Why it works: The plan starts from what’s actually on your plate, not what you remember while typing. From there, the model shapes the week around how you work. Deep work stays in big blocks if that’s how you operate, and there’s room built in for the day going differently than planned.

One gap: The model can’t tell how long your tasks take. A job that needs 2 full days can get squeezed into an afternoon.

Simple fix: Put a rough time next to each task, even a guess.

The Teardown

The book summary prompt that asks for everything

Maybe you want a summary to keep, so a book you read stays with you. Maybe you want to know what a book is about before you commit, or decide if it’s worth your time at all. Different jobs, and they don’t want the same prompt.

The one going around does the first job. It asks for everything worth knowing in one pass.

Write a thorough yet concise summary of [BOOK TITLE] by [AUTHOR]. Include 3 best quotes, main topic/theme, why someone should read it, 7-10 key ideas, chapter titles, key takeaways, techniques/processes, author background, comparison to similar books, 5-7 target audience groups, reception/critical response, recommendations for similar books, and a 1-2 sentence biggest takeaway.

That’s 12 things to include, with “concise” sitting at the front hoping to be heard.

Prompt Teardown

For an archive, this is fine. If you’re saving a book to your notes to come back to, more detail is the point, and the model handles it well. It doesn’t drone, it just covers the list.

The trouble is it has one setting. Everything, at equal weight. Nothing tells it which of the 12 matter most, so you get chapter titles and target-audience groups whether you wanted them or not. And if the book is fiction, everything includes the ending. Spoiler alert!

So it’s really 2 prompts. The full archive above, and a lean one for when you just want to know the book.

Build Up

Tell it what matters & let it drop the rest.

Summarize [BOOK] by [AUTHOR] in 4 parts:

1. One line: what it's about.

2. The 2 or 3 things worth taking from it, an idea if it teaches, a moment if it's a story, without giving away the ending.

3. 3 books like it, and how each one's close.

4. Who it's for, and who should skip it.

Keep it under 200 words, and don't spoil the book.

4 parts instead of 12, ranked by what a reader actually uses. The word cap forces the cut the original never made.

Ask for everything & concise is the first thing to die. Ask for what matters & concise is just what happens.

Related posts

  • Productivity The prompts people save vs. the prompts that work
  • Email The best prompts on Reddit this week
  • Workflows How to use AI to find the best hotel for your trip

Contents

  • The Take
  • Seen This Week
  • 1. The prompt that rewrites your email before you send it
  • 2. The prompt that plans an entire week you can finish
  • The Teardown
  • The book summary prompt that asks for everything
  • Prompt Teardown
  • Build Up

Get the next teardown

Free weekly prompt breakdowns.

In this article

  • The Take
  • Seen This Week
  • 1. The prompt that rewrites your email before you send it
  • 2. The prompt that plans an entire week you can finish
  • The Teardown
  • The book summary prompt that asks for everything
  • Prompt Teardown
  • Build Up

Frequently asked questions

How do I get AI to actually rewrite an email instead of just swapping in fancier words?

Make it read the email cold before it touches a single word. A plain 'improve this email' runs a thesaurus over your sentences and hands back the same structure in nicer clothes. Instead, tell it to first name who the reader is and what you're asking them to do, then list where the email falls short of that, then rewrite with permission to restructure freely in your voice. Naming the goal is what lets it rebuild the email rather than repaint it.

Does AI write a better email if I tell it who the recipient is?

Usually you don't have to. A capable model infers the reader from the email itself and matches tone to the relationship: cautious for a client you can't afford to lose, relaxed for a contractor who works for you. Spell it out only when the relationship isn't obvious from the text. The step actually worth doing is reading the rewrite for any reasoning it invented, like a reason for a late payment you never gave it, and cutting that before you send.

How do I plan my week with AI if my tasks aren't in a calendar or task app?

Do a brain dump first, then feed that list to the planner. Ask the model to have you empty everything on your plate into your own words, messy is fine, then read it back so you catch what you forgot. There's a fuller version in the brain dump prompt here. Once the list exists on paper, the weekly planner has something real to build from instead of trusting you to remember it all while typing.

Should I use a detailed book summary prompt or a short one?

Use the detailed one when you're archiving a book you've read and want to come back to. It covers quotes, chapters, key ideas, audience, and reception, so nothing is lost in your notes. Use the short one when you just want to know what a book is about before you commit your time. It caps the answer at what it's about, what to take from it, a few similar books, and who it's for, in under 200 words with no spoilers. Same book, two jobs, and forcing one prompt to do both is why concise never survives.

Weekly Teardowns ✦ Model Agnostic ✦ Steal These Prompts ✦ Weekly Teardowns ✦ Model Agnostic ✦ Steal These Prompts ✦ Weekly Teardowns ✦ Model Agnostic ✦ Steal These Prompts ✦
Prompt Teardown

Weekly prompt teardowns for people who take AI seriously. Model-agnostic.

Site

  • Blog
  • Archive
  • Sponsor
© 2026 Prompt Teardown
Prompt Teardown

Prompt Teardown

Add your email to get weekly prompts in your inbox.

Click subscribe to get started. Tap subscribe to get started.

We hate spam, too.
We only send 1 email a week. Unsubscribe anytime.