Have your AI write the email, not the answer

#The situation

There is a topic you are working on and it has a folder. A client, a negotiation, a supplier, a project — whichever it is, the folder has the contract in it, the notes from the last call, the numbers, the thread of what has already been agreed. You gave your assistant access to that folder, and that one decision changed the quality of everything it produces, because it is no longer guessing at context you never gave it.

So you ask it to draft the email. And it does, and the draft is good — it knows the name, it knows what was promised in March, it knows the number you are not willing to go below.

Then you have to get it out of the chat.

If you are working in a terminal, you select the reply and copy it. What lands in your mail client is a wall of text with the line breaks in the wrong places, the bullet characters turned into hyphens, the bold markers still visible as asterisks, and a paragraph gap where there should not be one. You spend two minutes fixing spacing in an email you did not write. If it had a table in it, you rewrite the table.

The first real improvement is obvious once you have done the copy-paste dance enough times: ask the assistant to write the email into the folder instead. Now it is a file. It is next to the contract it refers to. When you come back in a week you do not have to scroll up through a conversation to find what you sent — you open the file.

That solves the finding problem. It does not solve the sending problem. The file sits there, correctly written, and you still have to open it, still have to select its contents, and still have to paste it somewhere.

The rest of this is about closing that last gap.

#Ask the AI

Two prompts. The first one is the setup, pasted once per project — into custom instructions, a CLAUDE.md, an AGENTS.md, a project's system prompt, wherever your assistant keeps standing orders. The second is what you actually type when you want an email.

The standing instruction:

When I ask you for an email, write it as a Markdown file in this folder
rather than as chat text. Use this shape:

---
to: someone@example.com
cc: []
subject: A specific subject line, not a label
---

Then the message body as normal Markdown — paragraphs, bold, lists,
tables where a table is genuinely clearer than prose.

Rules:
- Put anything that is for me and must never be sent between
  <!-- send:skip --> and <!-- /send:skip -->.
- If you are unsure between two wordings, give me both, each under
  <!-- send:option Short label --> and let me pick.
- Name the file so I recognise it in six months: who, what, date.
- Read the folder before you write. Use the real names, the real
  numbers and what was actually agreed. Do not invent a detail to
  make a sentence work — if something is missing, put the question
  in the skip block.

The ask:

Read the notes from Tuesday's call and the current contract, then draft
the email to Marta confirming the revised delivery window. Firm on the
date, warm on the tone. Flag anything in the contract that contradicts
what we agreed on the call.

That second prompt is short because the first one did the work, and because the folder did the rest. Nothing in it explains who Marta is.

The reason the standing instruction is worth pasting once is the send:skip rule. A real draft is a working document — it carries the assistant's caveats, the thing it was not sure about, the reminder that the contract says something different. You want all of that. You just do not want to send it. Without a convention for marking it, you get one of two bad outcomes: an assistant that suppresses its own doubts to keep the draft clean, or a draft you have to proofread for leaks every single time.

#What comes back

A file. Something like marta-delivery-window-2026-09-16.md:

---
to: marta@example.com
cc: [ops@example.com]
subject: Revised delivery window — confirming 14 November
---

Hi Marta,

Following our call on Tuesday, I'm writing to confirm the revised
delivery window we agreed:

| Milestone            | Original   | Revised     |
| -------------------- | ---------- | ----------- |
| Design sign-off      | 2 Oct      | 2 Oct       |
| Production start     | 14 Oct     | 21 Oct      |
| Delivery             | 31 Oct     | **14 Nov**  |

The two-week shift sits entirely in production. Design sign-off is
unchanged, so nothing on your side moves.

I've asked the team to treat 14 November as firm. If anything
threatens it, you'll hear it from me before it becomes a problem
rather than after.

Thanks for the flexibility on this one.

Best,
Amílcar

<!-- send:skip -->
Note for you, not for Marta: clause 7.2 of the signed contract still
says 31 October and carries a late-delivery penalty. The call agreed
the extension verbally but nothing has amended the contract. Either
add a line asking her to confirm the amendment in writing, or send
this and follow up with a formal variation — but do not leave it
implicit.
<!-- /send:skip -->

Read that skip block again. It is the most valuable part of the file and it is the part that must never reach Marta. An assistant with a folder will find things like this, if you give it somewhere safe to put them.

#Save it as a file

It already is one. That is the whole trick — you did not ask for an answer and then save it, you asked for a file and got one, in the folder where it belongs, sitting next to the contract it is arguing about.

What remains is opening it, and this is where MD Flow does its one job. Point it at the folder and the file renders: the table is a table, the bold is bold, the frontmatter becomes a tidy header instead of a wall of dashes. It is a reading view, not an editor — it never modifies what it reads, which matters when the thing reading your folder is not the only thing writing to it.

Because the file has a to: line, MD Flow also recognises it as a draft. Recipients and subject appear above the document, and a Compose button appears with them. Pressing it opens the message, already written, in your mail client — Mail, Gmail or Outlook, whichever you set in Settings, or ask each time if you switch between work and personal. The skip block does not come with it.

Then you read it once more as an email rather than as a document, fix the one sentence that always needs fixing, and send it.

One honest caveat, because it is the kind of thing you should hear before you rely on it: Gmail and Outlook receive the body as plain text. Their compose links carry the message as a URL parameter, which cannot express a bold run or a table no matter how it is encoded. The default mail app keeps the formatting. When a draft has formatting that would be lost, MD Flow says so and offers the formatted version on the clipboard instead, so one paste restores it — and it remembers which you prefer. Compose is part of Pro, a one-time unlock rather than a subscription; reading, rendering, browsing and search by filename are free.

#Why that matters next week

The copy-paste was never the expensive part. Two minutes, a few times a day — annoying, survivable. What the copy-paste costs you is everything that happens after.

The correction loop collapses. Marta replies, and something in your email was wrong. If the email lived in a chat window, you are back in a conversation you have lost the thread of, re-explaining context to get one paragraph changed. If it lives in the folder, you say the delivery date moved to the 21st, update the draft and flag anything downstream that breaks. The assistant opens the file it wrote, and it can see the contract too.

You have a record of what you actually sent. Not of what you intended to send, not of what the assistant proposed — the file that produced the message. When the question in February is what exactly did we tell them about the penalty clause, the answer is in a folder with a name on it, and it is readable on your phone, because the folder syncs.

The doubts survive. That note about clause 7.2 is still in the file. It was never sent, and it was never lost either. Six weeks later, when the variation still has not been signed, the file is the thing that reminds you.

And the folder gets better. Every artifact you keep is context for the next one. The next email to Marta is drafted by an assistant that can read the last one. This is the part people underestimate about giving an AI a folder: it is not a filing habit, it is compounding. The reason to keep the output is that it becomes the input.

The chat window was always the wrong container. It is a transcript of a conversation, and nobody re-reads a transcript. A folder of files is a place things accumulate, and a rendered file is something you will actually open.

Give the assistant the folder. Ask it for files. Then all you need is something that opens them.