From Prompter to System Designer

Definition-of-done, handoff format, and stop-condition templates for designing loops instead of prompts.

Author
@cyrilXBT
Tags
loopsagents
NO.019Filed 2026-07-23

Step 5: Write The Definition Of Done Before Writing Any Prompt

DEFINITION OF DONE for [task name]:
- [Specific, checkable criterion 1]
- [Specific, checkable criterion 2]
- [Specific, checkable criterion 3]
This task is NOT done if any of the above is missing, even if the output
looks complete or polished.

Step 8: Write The Handoff Format Before You Write The Handoff Prompt

BUILDER OUTPUT: deliverable + confidence + known uncertainties
JUDGE VERDICT: PASS / FAIL / NEEDS REVISION + specific issues found +
what ground truth this was checked against

Step 10: Build The Manager And Its Stop Condition

STOP CONDITIONS:
Maximum revisions: 3. On the 3rd failed verdict, escalate to a human
with the full history, do not attempt a 4th cycle.
Quality threshold: every item in the definition of done must show PASS.
Budget ceiling: if this task exceeds [X] cost or [Y] time, stop
immediately regardless of current state.