Check the fix resolved the breakpoint without regressions
Packaged know-how that tells an agent how to do a job well.
You might say…
“A fix that closed one problem and opened another wasn't a fix — this pass is how I found out which kind I'd made.”
What it does
Reviews the next case's output against the edited step or template to confirm the change produced the intended result, and scans adjacent steps for regressions the fix may have introduced.
Trigger: Use on the next delivery after a change is committed, as the targeted verification before any wider rollout decision.
I/O: Edited method artefact + next-case delivery output → verification result (resolved/not-resolved) with regression scan across adjacent steps
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation