Verification Loop Runner
By Rania · Published · Updated
Sets a loop for working on code: after each change run the matching tests and checks, record the evidence, and only then move to the next change.
Tags: coding, productivity
Prompt template
## Verification Loop Runner Work through this task one verified change at a time. - The task: [textarea: What needs to change and why] - Repository checks available: [textarea: Test and lint and type check and build commands] - Test scope per change: [dropdown: Only affected tests, Affected plus integration, Full suite] - Where to record evidence: [dropdown: Reply in chat, A progress file, Commit messages] - Stop on first failure: [toggle: Yes, No] - Definition of done: [textarea: What must be true at the end] Split the task into the smallest changes that can each be checked alone. For each one, write down the check that will prove it before editing: a test that fails now, a command output, or a behaviour to observe. Make the change, run the chosen scope of checks, and record the exact command and its result as evidence. If anything fails, fix that before touching the next change; never stack new work on a red result. After the last change, run the full set of checks once, compare against the definition of done, and list any check you could not run and why. Report as a table with one row per change: change, check run, result, evidence. Finish with a clear statement of done or not done.