Define done before Codex starts

Set the completion contract up front, track proof for every requirement, and block partial work from being called done.

Use this when

Use this for long-running Codex work, pull requests, runtime checks, or user-visible artifacts where a plausible partial result could be mistaken for completion.

How it runs

1. Recover a measurable definition of done for every ambiguous requirement.
2. Record the requirements, scope, non-goals, evidence plan, and current status without expanding the requested work.
3. Execute one bounded action at a time and attach current evidence to each affected requirement.
4. Audit every requirement before closure and preserve honest blocked, exhausted, stalled, or contradicted states.

Done when

✓ Every Codex Goal requirement has current, adequate proof. The final audit contains no weak, missing, or contradicted required item; otherwise the work remains open, blocked, or exhausted.

Why it works

A durable completion contract keeps the definition of done visible across long sessions. Mapping every requirement to evidence makes false completion easy to detect.

Implementation note

Use $goal-planner-codex only when the user explicitly asks for a Codex Goal or completion audit. Create native Goal state only with approval; ordinary task planning does not need it, and budget exhaustion never counts as success.

Source: Forward Future ↗

More maintenance loops