Skip to main content

Use caseWrite

Turn a week of reading notes into something you can publish

One finished piece — a post, a memo, a newsletter section — written from notes you already had, where every quote you relied on still opens the page it came from.

You start with
A week or two of reading notes in your folder — adopted annotations, reading write-ups, kept answers, quick notes — next to the documents they are about. A mess is fine.
Time
An afternoon.
Your part
Most of it. Retrieval, structure suggestions and line editing are handed over; the argument keeps coming back to you.
DownloadSee the steps ↓

What you'll end up with

  • A piece of roughly eight hundred to two thousand words, built on an argument you wrote yourself.
  • Claims you can open and land on the page in the paper that justified them — the notes never stopped being attached to their sources.
  • The piece back in the same folder, where next month's questions can quote it alongside the papers and notes behind it.

That last one is the loop: the folder gets more useful each time you write out of it.

How to turn reading notes into a published piece, step by step

  1. Find out what you have actually been circling.

    You ask · MindMax answers

    AskWhat have my notes from the last two weeks kept coming back to?

    Notes and the documents behind them are searched together, so the answer is built from both. If the week is scattered quick notes, press Tidy whole note on them first — grouped points read better than fragments.

  2. Push for the argument, not the topic.

    You ask · MindMax answers

    AskWhat claim do these notes support that I have not written down anywhere?

    A topic gets you a listicle. Expect to reject the first answer — it will be the safe one.

  3. Write the spine yourself.

    You

    Five or six lines in a new note, each one a step in the argument. Fifteen minutes, and the difference between a piece and a pile. Nothing downstream can fix a spine you skipped.

  4. Draft section by section at the cursor.

    You ask · MindMax answers

    Under each line of the spine, call the AI where you are: continue, draft this section, tighten this paragraph. Every rewrite arrives as a tracked change, so a sentence you liked never silently disappears.

  5. Pull the evidence back in.

    You

    Where the draft asserts something you read, bring the actual quote. Search the folder when you remember the wording; when you only remember the idea, ask the assistant — it reads the candidates rather than matching your words.

  6. Read it once with the AI switched off.

    You

    The last pass is yours. It is where you find the two paragraphs that sound fluent and say nothing — the characteristic failure of writing this way.

  7. Send it out.

    You

    Keep it as Markdown, or export to Word or PDF for someone who wants a document. The source file stays in your folder either way.

Why it works here

Your notes and your sources answer together

One question searches the notes and the documents they are about, so what comes back is built from your reactions and the evidence behind them.

Ask questions across a folder →

AI at the cursor, as tracked changes

Drafting and tightening happen where you are writing, and every rewrite is a change you accept or reject — not a new version to diff by eye.

Markdown editor with an inline AI →

Find the passage by word or by asking

Search finds the wording you remember; the assistant reads candidates when you only remember the idea.

Search your folder →

Also used here: AI quick notes · Export to Word and PDF · Guide: writing in the editor

Where it gets hard

  • Highlights are not notes.

    If your week produced underlined sentences and none of your own, there is nothing to write back from. Adopted annotations and reading write-ups count; a wall of yellow does not.

  • "Make it sound like me" does not work.

    Grammar, tightening and structure are reliable. Voice is not, and no prompting fixes it. Reject and rewrite is faster than negotiating.

  • Whole-draft changes are a different tool.

    At the cursor, keep requests to a paragraph or a section. When the problem is the whole piece — drifting terminology, an order that does not work — leave comments or use /rewrite, and edits come back grouped with reasons.

  • Moving files afterwards can strand a citation.

    If you reorganise the folder mid-draft, check that the links still open what they should before you publish.

  • The piece will be as good as the argument in step 3.

    Everything after it is execution, and execution cannot rescue a claim you did not actually have.

Then what

A project that runs for weeks

Write a thesis or a book

When the piece turns out to be a chapter.

About an hour

Turn feedback on a draft into a second draft

When someone reads it and comes back with comments.

DownloadAll use cases