Learn · Configuration & workflows · CCAR-F task 3.5

Iterative refinement

Concrete examples, failing tests, an interview first, sensible batching and early course-correction: how to steer Claude to the right result.

Key ideas

• Give 2-3 concrete input/output examples instead of describing the result abstractly.
• Test-driven iteration: write or point to failing tests and let Claude iterate until they pass.
• Use the interview pattern: have Claude ask clarifying questions before a large feature.
• Batch interacting issues in one message; fix independent issues one at a time.
• Course-correct early with Esc, /rewind or /clear and a restated task.

Worked example: Pinning down a format

Instead of 'make the dates nicer', give examples and a test target.

Exam traps

• Describing the desired output in adjectives when two examples would remove the ambiguity.
• Sending several unrelated fixes in one message, so no single change is verifiable.
• Splitting interacting issues across messages, so each fix breaks another.
• Stacking corrections onto a confused conversation instead of interrupting or clearing.

Official docs

• Common workflows

Practise CCAR-F questions · Next lesson: Claude Code in CI/CD