Use caseWrite
Turn feedback on a draft into a second draft
A second draft in which every change answers a specific piece of feedback — reviewed group by group as tracked changes, with the feedback you chose not to act on still open.
- You start with
- A draft you wrote, as Markdown in your folder, and feedback on it — from a supervisor, an editor, a reviewer, or yourself a week later.
- Time
- About an hour for a chapter-sized draft.
- Your part
- Most of it: placing the feedback and reviewing the changes. Drafting the edits is not yours.
What you'll end up with
- A second draft where every change names the comment it answers.
- The feedback you decided not to act on, still open, so it does not quietly disappear.
- No new document to re-read from the top to find out what happened to it.
That last one is the usual cost of asking an AI to “apply these comments” — and the thing this workflow removes.
How to revise a draft from feedback, step by step
Read the feedback once, all the way through.
YouBefore touching anything, sort it in your head: what you agree with, what you do not, and what is a question rather than an instruction.
Put each point on the passage it is about.
YouSelect the passage and leave a comment. Feedback from a separate document gets translated here — "the methods are unclear about sampling" becomes a comment on that paragraph. Feedback you disagree with stays out.
Write the comment as an instruction, not a mood.
You"Unclear" is a mood. "Say how participants were recruited before giving the numbers" is an instruction. The AI can only make the edit you describe — and you can check the result against it in two seconds.
For whole-draft points, say them instead.
You ask · MindMax answersAsk/rewrite The terminology drifts between chapters — make it consistent.
Some points are not about any one passage. With the document open, type /rewrite in the assistant and say it; it reads the whole draft and edits wherever the drift is.
Press Revise from all.
MindMaxIt is the main button at the top of the comments panel. To work in batches — structure first, wording later — tick the comments for this round and revise from just those.
Read the reasons before the edits.
YouChanges come back in groups, each with a title, a one-line reason and the comment it answers. Skim the reasons first: they tell you which groups need a close look.
Accept, reject, apply.
YouA rejected group leaves its comment open, so you can rephrase it and try again, or make the edit yourself. On apply, comments behind accepted groups are marked done — what stays open is exactly what you have not dealt with.
Why it works here
Every edit answers a comment
Edits come back grouped, each with its reason and the comment it answers — so you judge them against what you asked for, not against a whole new draft.
Whole-document revision →Nothing changes until you accept it
Groups arrive as tracked changes. Accept one, reject another; a rejected group keeps its comment open instead of losing it.
How review works →The draft and the comments live in one file
You write, comment and revise in the same Markdown editor, in your own folder — no copying between a chat window and a document.
Markdown editor →Also used here: Skills you can write yourself · Guide: writing in the editor
Where it gets hard
- Feedback in a Word file or a PDF does not come across by itself.
Comments someone left in Word are not imported. Step 2 is you deciding where each point lands — which is where most of the judgement in a revision happens.
- Revising from comments needs a document you write in.
Comments become edits on Markdown documents. For a draft that lives as a Word file, put the feedback into one request in the assistant instead — the accepted edits go back into the .docx as Word tracked changes. Comments on PDFs and ebooks get answers, not edits.
- "Make it flow better" gets you a generic edit.
Vague feedback produces vague changes. The more specific the comment, the less there is to review.
- It will not sound like you.
Restructuring, tightening and consistency are reliable; voice is not. Reject those groups and write the sentence yourself.
- Review is still real work.
Thirty comments mean a lot of groups to judge. That is the point — but budget for it, and work in batches if the draft is long.
Then what
About an hour
The other side: when you are the one giving the feedback.
A project that runs for weeks
When the draft itself is what you need help producing.
An afternoon
The step before a draft exists.