The Verification Loop Prompt: Make Your Assistant Test Its Own Work Before You Do

If you use an assistant for coding or writing, you’ve probably seen this pattern: You ask for something concrete. You get something that looks right. You spend the next 20 minutes discovering the hidden gotchas. The fix isn’t “use a better model” or “be more specific” (though both help). The fix is to change the shape of the request. I call it the Verification Loop Prompt : a two-phase prompt that forces the assistant to test and interrogate its own output before handing it to you. This is not about perfection. It’s about catching the top 80% of failure modes—early, cheaply, and repeatably. The idea Most prompts ask for an answer . The Verification Loop asks for an answer + evidence . You’re not just requesting “do X”. You’re requesting: Generate the solution. Verify it against constraints, edge cases, and a small test plan. Report what’s still uncertain. That last step matters: a good verification loop doesn’t pretend certainty—it surfaces it . The base prompt (copy/paste) Use this as