Verification-first development
An approach where the checks that would accept a change are set up first, so the checks decide when the work is done.
Verification-first development asks one question before any code is written. What would have to pass for this change to count as done? The answer might be tests, lint rules, a repeatable failing case, or a measurable behavior. You set that up first. The code then works toward it. Test-driven development is the oldest member of this family. The idea extends to any mechanical check.
This matters more with coding agents than it did with humans, because agents write confident prose about their own work. A model will say the fix is complete whether or not it is. A failing check cannot be talked around. Tying done-ness to checks turns a trust problem into an engineering problem.
The discipline has a known failure mode. Checks can pass while testing nothing, or get quietly weakened to go green. So the practice includes grading the checks themselves. Making a check fail on purpose, once, is the cheapest way to learn whether it can.