[Feature Request] Add mandatory acceptance testing step before final output submission

Status Open
Reported on v2.1.238
Maintainer reply None cached
Activity 0 comments · opened Aug 22, 2026

Bug Description
Claude in coding and programming NEVER REALLY CHECKS HIS FINAL OUTPUTS AGAINST THE ORIGINAL PROMPT: he never makes any acceptance tests, FAT, commissioning of the results of his job once it is done, against the original requirements by the customer. It works blindly just one-way, basing on his knowledge, but many times the human opening its output finds rapidly some apparent mistakes or malfunctions that make the work by Claude incorrect, not working or simply not satisfying his original instructions.

In Italy we call it "LAVORARE ALLA CIECA" (to work blindly, without measuring the results), like a blind cook putting ingredients and salt into his pan and never tasting the food he is making, since he is such confident on the recipe and his knowledge. That does not work at all most of times, and the customer refuse the final dish since it has defect he can see or taste immediately as soon as he receives the dish and start eating. Sometimes it is enough just to taste the final dish you cooked before serving it to the customer, and great chefs just do it.
What if some of your ingredients were already salty, and you assume they are not? You put some other salt. And if you don't taste the final dish that you are serving, the customer returns it back to you saying "that's too salty", with a lot of frustration (since he has also waited a lot for his dish=claude output, many times ;) ). the cook in the kitchen then tastes it and agrees it's too salty, but the bad impression on the client is done and some could think he is unreliable, unprofessional.

It would be indeed just a matter of prompt to remind him EVERY SINGLE TIME to inspect (like in machinery acceptance) his final result before submitting it to the customer. Most of mistakes and errors are rapidly solved by implementing this feedback loop. But I think a structural intervention by programmers in the fundamental prompts would definitely be a turning point, avoiding us to remind him at various levels of prompting this fundamental need.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.238
  • Feedback ID: b012eff5-04b9-43ca-bb9d-1339ec4ff8f6

Errors

[]

View original on GitHub ↗