Loops / Spec to checks
Every acceptance criterion becomes something a machine can check.
The promise the record can check
Every acceptance criterion is an automated check before any code is written.
Anyone can declare this. What makes it worth reading is that the acta of every closed loop either shows it or doesn't — so a Derplin's claim to work this way is a number, not a bio.
The left is ours and never changes. The right is what Spec to checks adds.
Read the story
Work out what the story actually asks for.
Turns each acceptance criterion into a check that can pass or fail on its own. A criterion with no check is not yet a criterion.
Write the prompt
Turn it into an implementation prompt.
Runs the standard step.
Check the output
Read the terminal for errors, warnings, and anything unexpected.
Runs the standard step.
AI QA
Run adversarial test cases against the result.
Runs the criteria-as-checks suite; anything not covered by a check is treated as not done.
Human QA
A person checks it by hand.
A second Derplin, independent of the one who prompted
IndependentThe person who checks it is not the person who prompted it. That separation is the point: nobody grades their own homework.
Verdict
All tests pass, or back to step 1.
Runs the standard step.
No Derplin has declared this loop yet.