CCAR-F objective 3.5 · Domain 3 · 20% of the exam

Iterative Refinement Techniques

Claude stops when the work looks done, and without something that returns pass or fail, looking done is the only signal available and you become the verification loop. So the answer is usually to give it a check it can run: a test suite, a build exit code, a script that diffs against a fixture. The mechanisms escalate from asking in the prompt, through a goal condition, to a Stop hook that blocks the turn from ending. Two counter-intuitive points: ask for evidence rather than an assertion of success, and after correcting the same issue twice, clear the context rather than correcting a third time.