A prompt that makes your AI write files, not replies

#The situation

You finish a call and paste your rough notes into ChatGPT: turn this into something I'll keep. It does, and the result is good. Clear headings, the action items pulled out, the risks spotted.

Then the conversation scrolls. Three weeks later someone asks what the client said about pricing, and you are scrolling a sidebar of chats named after the first thing you typed, trying to remember which one it was.

The work was fine. The container was wrong. A chat reply is a message, and messages are made to be read once. What you wanted was a document: something with a name, a date and a place to live.

You can fix that in the assistant rather than in yourself. Tell it once what a keepable answer looks like, and it will hand every one of them back as a file.

#Ask the AI

Paste this once, wherever your assistant keeps standing orders: custom instructions or a project's instructions in ChatGPT, a project's instructions in Claude, or a CLAUDE.md / AGENTS.md for an agent that works in a folder.

From now on, when I ask for something I'm likely to keep — a summary, a plan,
research, a comparison, a checklist, notes — give it to me as a Markdown file,
not a chat reply.

The file:
- Starts with frontmatter:
  ---
  title: What this is, specific enough to recognise in six months
  date: YYYY-MM-DD (today)
  type: one of summary, plan, research, comparison, checklist, notes
  status: draft
  ---
- Then one # heading that repeats the title, and a two-sentence summary under it.
- Uses ## sections, tables where comparing things, - [ ] for anything someone
  has to do, and > [!warning] for risks or things I must not miss.
- Ends with a "## Open questions" section listing what you didn't know or had
  to assume. Don't invent facts to fill a gap; put the gap here.
- Has a filename: lowercase words joined by hyphens, what it is, then the
  date. Example: q4-pricing-options-2026-10-02.md

If you can write files in my folder, save it there and tell me the filename.
If you can't, reply with the filename on the first line and the whole file in
one ```markdown block, and nothing after the block.

Short questions and quick answers stay as normal chat replies.

Three lines in it do most of the work.

The filename rule. The name is the only metadata that survives every export, sync and migration. What it is, then the date is the pattern you will actually search for later.

Open questions. Assistants fill gaps to make a paragraph read smoothly. Giving the uncertainty its own section, and saying it is welcome there, is the most reliable way to stop that.

The fork at the end. An agent that can write to disk just writes the file. A chat assistant can't, so it hands you the file in one block with its name on top, and saving it is one copy. Everything else stays a normal conversation, so the instruction doesn't turn what's 15% of 340 into a document.

Then ask the way you always do:

Here are my rough notes from today's call with Northwind. Turn them into
something I'll keep.

- spoke to Dana (ops lead) + Luis (finance)
- they run 3 depots, ~60 vans, planning done in spreadsheets each morning, takes 2h
- main pain: last-minute order changes, re-planning by hand
- Luis worried about price per van, they pay 18/van/month for current GPS tracking
- want to trial with 1 depot first, 4 weeks
- need it to import from their order system (it's "Cargotrack"? Dana wasn't sure of version)
- decision by end of Nov, budget cycle starts Dec
- Dana asked if drivers need a new app or if it works on their current phones (android, some old)
- I promised to send pricing options + trial plan by Friday

#What comes back

This is a real run of that prompt, shortened for the page: an attendees list, a third warning and one open question are cut, and a few bullets are condensed. The first line is the filename, then the file:

northwind-call-notes-2026-09-26.md

---
title: Northwind discovery call — ops/finance pain points and trial ask
date: 2026-09-26
type: notes
status: draft
---

# Northwind discovery call — ops/finance pain points and trial ask

Northwind (40-person logistics company, 3 depots, ~60 vans) is evaluating our
route-planning tool to replace manual spreadsheet planning. They want a
single-depot, 4-week trial and a decision by end of November, ahead of their
December budget cycle.

## Current state

- Planning done manually in spreadsheets each morning, taking ~2 hours per day
- Main pain point: last-minute order changes force manual re-planning
- Currently pay $18/van/month for existing GPS tracking (Luis's reference point
  for pricing)

## What they're asking for

- [ ] Pricing options (Luis will compare against the $18/van/month baseline)
- [ ] A trial plan: 1 depot first, 4 weeks
- [ ] Confirmation on order system import — "Cargotrack" (version unconfirmed)
- [ ] Answer on driver app requirements — new app, or their current Android
      phones (some older models)?

## Timeline

- Decision needed by end of November 2026; their budget cycle starts December
- **Commitment made:** send pricing options + trial plan by Friday

> [!warning]
> Budget cycle starts in December — missing the end-of-November decision
> window likely pushes any deal to next cycle.

> [!warning]
> Cargotrack integration is unconfirmed — verify API/export compatibility
> before committing to an import timeline in the trial plan.

## Open questions

- Which Cargotrack version Northwind runs, and whether it has an API or export
  format we support
- Minimum Android version our driver app requires, versus what Northwind's
  older phones can run
- Which depot Northwind wants to use for the trial (not discussed on the call)
- Whether "Friday" means 2026-10-02 — not stated explicitly on the call

Two things to notice, one good and one a warning.

The good one: the last two open questions are things the notes left open. Nobody said which depot, and "Friday" is ambiguous from a Saturday. The assistant said so instead of quietly picking one. That's the open-questions line doing its job.

The warning: the notes said 18/van/month, and the file says $18. The currency was a guess. That's exactly the kind of fill-in the instruction asks it not to make, and it made it anyway. A file you will reread next month deserves one read now, while you still remember the call.

#Save it as a file

Save the block as the file it names, in the folder for that client, and open that folder in MD Flow (what browsing a folder of Markdown looks like).

The frontmatter becomes a tidy header instead of a wall of dashes, the warnings render as coloured callouts, and the checklist is a checklist. MD Flow also ships a guide to the conventions it understands, ready to hand to whichever AI writes your files, so you can extend this prompt with the rest of what the app can render.

#Why that matters next week

You'll find it by name. northwind-call-notes-2026-09-26.md sorts next to the other Northwind files and turns up when you search for northwind. No chat history has ever made that easy. Search by filename is free in MD Flow. With Pro, search also reaches inside the files, so Cargotrack finds this document even though the word isn't in its name.

The open questions become Friday's to-do list. You promised pricing and a trial plan. The file tells you the three things to find out first, and it's still telling you on Thursday, when the chat would have scrolled away.

The next document starts from this one. When you draft the trial plan, give the assistant this file instead of retyping the context. Every file you keep is context for the next one, which is the argument of where to keep what your AI writes, and it only works if the output was a file in the first place.

The status field keeps you honest. Everything starts as draft. When you've checked the currency and the date, change it. Six months from now, a folder where some notes say draft and some don't tells you which ones you actually verified.

One instruction, pasted once. After that, anything worth keeping arrives as something you can keep.