Iterate, Don't Rewrite

Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't working. Here's how to iterate like a craftsperson.

22 min · Reviewed 2026

The rewrite trap

When a prompt gives a bad output, the temptation is to throw it out and type a fresh one. Don't. The first prompt probably had 80% of the right stuff. You just need to fix the 20% that's off.

The diagnostic loop

Run the prompt. Look at the output.
Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
Change only the part related to that problem.
Run again. Compare.
If it got worse, undo. If it got better, keep going.

Version diary example

v1: Write a product description for a reusable water bottle.
→ Output: Generic marketing speak.

v2 (added audience): Write a product description for a reusable water bottle targeting eco-conscious college students.
→ Output: Better but still too 'ad-like.'

v3 (added role and tone): You are a copywriter for a zero-waste brand. Write a product description for a reusable water bottle. Tone: warm, punchy, no clichés like 'game-changer.'
→ Output: Much better. Reads like a real brand.

v4 (added format): ...as v3, but output with a hooky headline, 2 short body sentences, and 3 bullet features.
→ Output: Ready to ship.Four versions, each isolating one change.

Each version changed one thing. That means if v3 was much better than v2, you know it was the role-and-tone addition. If you had changed three things at once, you wouldn't know what helped.

Keep a prompt notebook

Save prompts that worked, with a note on what task they solved.
Save prompts that failed, with a note on what broke.
Steal from your past self. The template you tuned last month is gold.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prompting-iteration-builders

What is the core idea behind "Iterate, Don't Rewrite"?
1. Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't working. Here's how to iterate like a craftsperson.
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which term best describes a foundational idea in "Iterate, Don't Rewrite"?
1. prompt versioning
2. iteration
3. expertise
4. Approximate paragraph counts and section headings.
A learner studying Iterate, Don't Rewrite would need to understand which concept?
1. iteration
2. expertise
3. prompt versioning
4. Approximate paragraph counts and section headings.
Which of these correctly reflects a principle in Iterate, Don't Rewrite?
1. Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
2. Change only the part related to that problem.
3. Run again. Compare.
4. Run the prompt. Look at the output.
Which of these does NOT belong in a discussion of Iterate, Don't Rewrite?
1. expertise
2. Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
3. Change only the part related to that problem.
4. Run the prompt. Look at the output.
What is one important takeaway from studying Iterate, Don't Rewrite?
1. Save prompts that failed, with a note on what broke.
2. Save prompts that worked, with a note on what task they solved.
3. Steal from your past self. The template you tuned last month is gold.
4. expertise
What is the key insight about "Think like an editor, not an author" in the context of Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Keep the scaffold. Tweak the weak parts. Track what you changed so you learn.
4. Solve all problems by adding more context
What is the recommended tip about "Level up your prompts" in the context of Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Solve all problems by adding more context
4. Add context before your request — role, background, constraints. A prompt like "You are a chemistry teacher.
Which statement accurately describes an aspect of Iterate, Don't Rewrite?
1. When a prompt gives a bad output, the temptation is to throw it out and type a fresh one. Don't.
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
What does working with Iterate, Don't Rewrite typically involve?
1. expertise
2. Each version changed one thing. That means if v3 was much better than v2, you know it was the role-and-tone addition.
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which best describes the scope of "Iterate, Don't Rewrite"?
1. It is unrelated to prompting workflows
2. It applies only to the opposite beginner tier
3. It focuses on Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't wor
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Solve all problems by adding more context
4. The diagnostic loop
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. Version diary example
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. expertise
2. Keep a prompt notebook
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which of the following is a concept covered in Iterate, Don't Rewrite?
1. prompt versioning
2. expertise
3. iteration
4. Approximate paragraph counts and section headings.

← Back to interactive lesson

Tendril · Builders · Prompting

Iterate, Don't Rewrite

Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't working. Here's how to iterate like a craftsperson.

22 min · Reviewed 2026

The rewrite trap

When a prompt gives a bad output, the temptation is to throw it out and type a fresh one. Don't. The first prompt probably had 80% of the right stuff. You just need to fix the 20% that's off.

The diagnostic loop

Run the prompt. Look at the output.
Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
Change only the part related to that problem.
Run again. Compare.
If it got worse, undo. If it got better, keep going.

Version diary example

v1: Write a product description for a reusable water bottle.
→ Output: Generic marketing speak.

v2 (added audience): Write a product description for a reusable water bottle targeting eco-conscious college students.
→ Output: Better but still too 'ad-like.'

v3 (added role and tone): You are a copywriter for a zero-waste brand. Write a product description for a reusable water bottle. Tone: warm, punchy, no clichés like 'game-changer.'
→ Output: Much better. Reads like a real brand.

v4 (added format): ...as v3, but output with a hooky headline, 2 short body sentences, and 3 bullet features.
→ Output: Ready to ship.Four versions, each isolating one change.

Each version changed one thing. That means if v3 was much better than v2, you know it was the role-and-tone addition. If you had changed three things at once, you wouldn't know what helped.

Keep a prompt notebook

Save prompts that worked, with a note on what task they solved.
Save prompts that failed, with a note on what broke.
Steal from your past self. The template you tuned last month is gold.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prompting-iteration-builders

What is the core idea behind "Iterate, Don't Rewrite"?
1. Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't working. Here's how to iterate like a craftsperson.
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which term best describes a foundational idea in "Iterate, Don't Rewrite"?
1. prompt versioning
2. iteration
3. expertise
4. Approximate paragraph counts and section headings.
A learner studying Iterate, Don't Rewrite would need to understand which concept?
1. iteration
2. expertise
3. prompt versioning
4. Approximate paragraph counts and section headings.
Which of these correctly reflects a principle in Iterate, Don't Rewrite?
1. Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
2. Change only the part related to that problem.
3. Run again. Compare.
4. Run the prompt. Look at the output.
Which of these does NOT belong in a discussion of Iterate, Don't Rewrite?
1. expertise
2. Identify exactly what's wrong (too long? wrong tone? missed a constraint?).
3. Change only the part related to that problem.
4. Run the prompt. Look at the output.
What is one important takeaway from studying Iterate, Don't Rewrite?
1. Save prompts that failed, with a note on what broke.
2. Save prompts that worked, with a note on what task they solved.
3. Steal from your past self. The template you tuned last month is gold.
4. expertise
What is the key insight about "Think like an editor, not an author" in the context of Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Keep the scaffold. Tweak the weak parts. Track what you changed so you learn.
4. Solve all problems by adding more context
What is the recommended tip about "Level up your prompts" in the context of Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Solve all problems by adding more context
4. Add context before your request — role, background, constraints. A prompt like "You are a chemistry teacher.
Which statement accurately describes an aspect of Iterate, Don't Rewrite?
1. When a prompt gives a bad output, the temptation is to throw it out and type a fresh one. Don't.
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
What does working with Iterate, Don't Rewrite typically involve?
1. expertise
2. Each version changed one thing. That means if v3 was much better than v2, you know it was the role-and-tone addition.
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which best describes the scope of "Iterate, Don't Rewrite"?
1. It is unrelated to prompting workflows
2. It applies only to the opposite beginner tier
3. It focuses on Beginners scrap their prompt and start over. Pros keep the good parts and change only what isn't wor
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. expertise
2. Approximate paragraph counts and section headings.
3. Solve all problems by adding more context
4. The diagnostic loop
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. Version diary example
2. expertise
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which section heading best belongs in a lesson about Iterate, Don't Rewrite?
1. expertise
2. Keep a prompt notebook
3. Approximate paragraph counts and section headings.
4. Solve all problems by adding more context
Which of the following is a concept covered in Iterate, Don't Rewrite?
1. prompt versioning
2. expertise
3. iteration
4. Approximate paragraph counts and section headings.

← Back to interactive lesson