ClaudeEditingLevel 2: Context

How Do You Get Honest Feedback on a Draft From Claude?

Ask for a critique and tell Claude not to rewrite anything. Name the reader, ask it to quote the exact lines it's commenting on, and have it rank the problems. You then choose what to fix, so the edit goes after real problems rather than Claude's guess at them.

Prompt to copy
Below is a draft I wrote. Don't rewrite anything yet.

<draft>
[paste the draft]
</draft>

The reader is [who they are and what they already know]. After reading, I want them to [decide, approve, do or understand what].

Critique it for that reader:
1. In one sentence, what will this reader take away, as written?
2. List the 5 problems most likely to stop them doing what I want, most serious first. Quote the exact words for each problem and say why it's a problem.
3. What would a skeptical reader object to that the draft doesn't answer?
4. What is working and should stay as it is?

If you can't judge something without information you don't have, say so.
Do
  • Name the reader
  • Ask for quoted lines
  • Have the problems ranked
  • Say not to rewrite
Don't
  • Let it rewrite straight away
  • Accept an unranked list of notes
  • Take a comment with no quote
A rule of thumb, not an Anthropic chart: a critique finds the problems, and you decide which to fix.

Try it now

  1. 1Attach or paste a draft you plan to send this week, and fill in the reader and goal.
  2. 2Compare Claude's one-sentence takeaway with what you meant. If they differ, that's your first problem.
  3. 3Pick the two or three problems you agree with, and ask for suggested fixes to only those.
  4. 4You'll know it worked when each note quotes real lines and you can disagree with it on specifics.

Use it when

Before a big edit, or when a draft feels off and you can't say why. It also works on a colleague's draft you've been asked to review, an application essay, or a pitch you're about to send to someone whose opinion matters.

Skip it when

Don't use it to settle facts. Claude can tell you a claim looks unsupported, but it can't confirm your company's numbers unless you give it the source. Skip it for a draft you already know is wrong in structure. Fix what you know first, or you'll get a long list about a version you're replacing.

Why it works

A critique separates finding problems from fixing them. A draft rewritten straight away hides the diagnosis: you can't tell which changes fixed something and which were just preference. Quoting lines makes the feedback checkable, and it's close to what Anthropic's docs recommend for long documents, which is having Claude quote relevant passages first so it focuses on the text itself.

A named reader gives Claude something to judge against. Anthropic's guide says context about why you want something helps Claude target its response. Rule of thumb, not a vendor figure: feedback gets sharper when you ask what a skeptical reader would object to, and when you ask for the problems ranked by how much they matter, since a flat list of 20 notes doesn't tell you where to start.

Example

Say you've written a one-page request to your director for a second support hire. You name the reader as a director who has already rejected one headcount request this year and cares about response times. Claude's job is to find what that person would push back on, such as a missing cost figure or a claim about ticket volume with no number behind it. It can only flag those as gaps. Attach your actual ticket report as well, and it can check your claims against it.

Going further

Let the critique live on the document. In Claude Docs, Anthropic's help page says Claude can leave its own comments explaining choices or asking questions, and you can reply by mentioning @Claude in a thread. So you can ask it to comment on the doc without changing any text, then resolve the notes one at a time. Open a comment box with Cmd+Option+M on Mac or Ctrl+Alt+M on Windows.

In Word, Claude's add-in can work through comment threads, editing the anchored text and replying with what it changed. In Google Docs it can't read comments at all, so paste a comment's text into the sidebar.

Common mistakes

  • Writing "what do you think?" with no reader. You'll get general notes on general writing, since Claude has nothing specific to judge against.
  • Saying it's your own work you're proud of, then asking for honesty. Rule of thumb: state the reader and goal, and leave out how you feel about the draft.
  • Forgetting "don't rewrite anything yet". On an open request, Anthropic's Sonnet 5.5 guide warns the model can start building things when you only wanted ideas.
  • Accepting every note. Claude doesn't know your reader as you do, so treat the list as options to choose from.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course