Write & communicate

Critique a draft before rewriting it

Diagnose the highest-impact problems without replacing the author’s intent

4 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

DraftPurpose and audienceConstraints

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Critique this draft before proposing any rewrite.

Purpose and audience:
[goal]

Constraints:
[constraints]

Draft:
[draft]

Evaluate the draft for goal alignment, clarity, evidence, structure, audience fit, and factual consistency. Quote short excerpts to locate each issue. Prioritize no more than five changes by impact.

Return:
1. What already works and should be preserved
2. High-impact issues, with evidence and consequence
3. Questions that must be answered before revision
4. A revision plan in priority order

Do not rewrite the draft unless I ask in a follow-up.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Draft: Join our neighborhood repair café next Saturday! Volunteers will help fix small household items, and the event will reduce waste for everyone. Bring lamps, toasters, clothing, or anything broken. The café runs from 10 a.m. to 1 p.m. at Riverside Community Room. Repairs are free, but parts might cost extra. We fixed nearly everything last time, so your item will probably leave working. Please arrive early because we may be busy. Children are welcome. Register through the form by Thursday.
Purpose and audience: A short email to neighborhood residents that explains the repair café and gets people with suitable items to register.
Constraints: Friendly and trustworthy tone; maximum 170 words; must retain the date wording, opening hours, venue, Thursday registration deadline, and possible parts cost. Do not promise that an item can be repaired.

Example output

What already works and should be preserved

The opening clearly identifies the event and timing. Examples such as “lamps, toasters, clothing” help residents judge relevance. The draft includes the hours, venue, registration deadline, free repair help, and possible parts cost. Its friendly tone suits a neighborhood email.

High-impact issues

“Your item will probably leave working” conflicts with the no-promise constraint and creates an expectation volunteers may not meet.
“Anything broken” is broader than “small household items.” Residents could register unsuitable or unsafe items.
“Next Saturday” is required, but no calendar date is supplied. Recipients who reopen or forward the email may not know which Saturday it means.
“Children are welcome” does not explain whether supervision or participation conditions apply. No additional rule should be invented.
“Please arrive early” is vague and competes with the stronger desired action: registering by Thursday.

Questions before revision

Which item types cannot be accepted? Does registration reserve a time or only estimate demand? What calendar date is next Saturday? Are there conditions attached to children attending?

Revision plan
Remove the repair-likelihood claim and state only what volunteers will attempt.
Define eligible items using confirmed limits.
Make Thursday registration the clearest call to action.
Add the calendar date if available while retaining “next Saturday.”
Clarify arrival and child-attendance guidance only after those details are confirmed.