Skip to main content

Refining Results with Claude Through Iteration

The first answer does not have to be perfect. By saying specifically what to change and continuing the conversation, you close in on the result you want.

🌐 This article was machine-translated and may contain inaccuracies. Read the Korean original if in doubt.

Claude's first answer does not have to be perfect. By saying specifically what you want changed and continuing the conversation, you steadily close in on the result you want. Getting a quick draft and refining it usually beats trying to nail it in one shot.

🟢 Model references match the current lineup · model notice · Fable subscription
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.

Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (

🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
0/M input, $50/M output tokens). The one-time
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
00 credit applied only to the Fable 5 transition and is not offered for 5.1. Some coding and debugging requests may be answered by an Opus model due to a security classifier (both models). See the Fable 5.1 guide and the Fable 5 availability guide for details.

Draft → Feedback → Final First draft roughly right Specific feedback "shorten this part" Final what you wanted → → refine again if needed

Do not aim for perfect in one shot

Complex outputs — long writing, code, plans — are hard to get perfect on the first try. Getting a quick draft and then pointing out what is missing takes less time and produces better results.

What makes feedback good

"What and how" to change works far better than "this is bad". For example: "the second paragraph is too long, cut it in half", "make the title more direct", "replace the example with a real case" — give both the target and the direction.

Common revision requests

  • Length: "shorter" / "more detail on this part only"
  • A specific part: "redo just the third item" — fix the spot you point to, not the whole thing.
  • Tone: "softer" / "more professional"
  • Add or remove: "add one example" / "drop the last paragraph"
Common revision requests Length shorter · more detail here Specific part redo just item 3 Tone softer · more professional Add / remove add example · drop a para

Editing vs starting fresh

Most of the time, continuing the conversation to edit is faster. But if you have revised so many times that the direction is tangled, or the original request was vague, it can be cleaner to gather your requirements and start a new conversation.

Worth knowing

As a conversation grows long, earlier context can fade. Restating the key constraints when you ask for a change keeps things stable. If results seem to be getting worse, collecting just the requirements you have settled on and starting fresh is a good option.

Related: 7 prompt-writing basics · controlling answer length

Reference: general prompting principles are documented in Anthropic's official docs (platform.claude.com/docs).

Was this helpful?

Keep reading