Quick fixes AG-P005
Make the next rewrite more useful
Shared methods · A shared method; linked tool guides explain the exact steps.
This page covers tools outside your selection. You can still read it. Find matching guides
Three rewrites without saying what was wrong is a slot machine, not editing. Name the gap, or start fresh — repeating "again" does neither.
I'm on the fourth rewrite and it's not improving? Here's the quick fix ↓ — the why sits right below it.
Quick fix: Make the next rewrite more useful
Instead of Try again. … No, again. … Still not right.
Try The last version lost the argument from paragraph two, and the tone got stiff. Restore that argument, keep the current length, loosen the tone.
Each retry must carry information about what was wrong. Otherwise you are re-rolling dice.
Why this works
The same request produces a different draw from the same distribution, so "again" gets you a sibling of the answer you disliked, not a correction of it. Worse, a long chain of rejected drafts stays in the conversation and keeps influencing the next one. Two exits: say precisely what the gap is (the model is good at applying a named correction), or accept that the framing itself is off and restart clean with a better request.
When this applies
You have asked for a redo three times, the versions feel interchangeable, and your instructions have degraded to "better", "no", or "again".
Template
Compared to what I want, the last version [what is wrong]. Keep [what it got right]. Change only [the specific gap].
If you cannot fill in the first line, the problem is upstream — you have not decided what you want yet, and no rewrite fixes that.
Go deeper
Naming the dimension of better is its own pattern. Knowing when to abandon a conversation instead of steering it is when to start fresh, including the signs a chat has gone bad underneath you.
Improve next
- Tell it what "better" means
Tell the AI what "better" means for this text.
- Say what you actually want
Tell the AI what outcome you actually want.
Something wrong with this page?
Say what you expected and what you got. That is usually the shortest route to a correction, and it goes on the public issue tracker so the fix is visible.