Positronick
← Registry
Loop Official

Checkpoint-Driven Execution

Write the success criteria and load-bearing assumptions first, complete exactly one step per pass while restating done / verified / left, and loop until every criterion is checked off and backed by evidence.

The methodology loop, not a gate loop. Iteration zero writes CHECKPOINT.md: the explicit, checkable success criteria as unchecked boxes plus every assumption the task rests on marked UNVERIFIED. Each subsequent pass does exactly one step — resolving an assumption by reading the artifact, or advancing one criterion — then appends a checkpoint stating what was done, what was verified (with the command output or file:line that proves it), and what remains, and refuses to proceed if it can't describe the current state back. Distinct from spec-first-ship (implements an external spec.md of feature requirements) and pr-self-review (reviews a finished diff): here the artifact is the agent's own evolving plan-and-evidence ledger.

Loop

Goal
every success criterion and assumption in CHECKPOINT.md is resolved — each checked off with a verification note (command output or file:line) proving it, or struck out as false with the correction noted
Exit when
CHECKPOINT.md exists with zero unchecked '- [ ]' boxes and zero UNVERIFIED entries, and every checked item carries a 'verified:' note

Check between iterations

test -f CHECKPOINT.md && grep -cE '^- \[ \]|UNVERIFIED' CHECKPOINT.md || echo MISSING_LEDGER
$

Kickoff prompt

Start the "Checkpoint-Driven Execution" loop. Goal: every success criterion and assumption in CHECKPOINT.md is resolved — each checked off with a verification note (command output or file:line) proving it, or struck out as false with the correction noted Max iterations: 12 Between iterations run: test -f CHECKPOINT.md && grep -cE '^- \[ \]|UNVERIFIED' CHECKPOINT.md || echo MISSING_LEDGER Exit when: CHECKPOINT.md exists with zero unchecked '- [ ]' boxes and zero UNVERIFIED entries, and every checked item carries a 'verified:' note Step 1: Before any code, write CHECKPOINT.md listing the explicit success criteria as '- [ ]' boxes and every assumption the task rests on as UNVERIFIED, then resolve one assumption or complete one criterion and append a checkpoint of what was done, what was verified (with evidence), and what remains.
›
Official source ↗