Run an exit check on the task most recently completed in this conversation or workspace. This check does not authorize additional work. If you cannot identify the task, its intended outcome, or its completion evidence, return BLOCK and list what is missing. Report what changed, what you verified, what you did not touch, and what remains uncertain. Classify the current task as PASS, DELAY, or BLOCK. Separately classify the next visible action as GO, HOLD, CAP, or BLOCK. Explain the decision briefly. If you choose CAP, define its exact scope and limit. Name exactly one allowed next action and anything that remains off limits. Do not begin the action, even if the result is GO. Stop and wait for the user. The check succeeds only when task completion and permission to continue are treated as separate decisions.
claude-code · codex
Use this when
Use this after an agent finishes a task and another visible action could tempt it to continue beyond the user's original request.
How it runs
Identify the completed task, its intended outcome, and the evidence available for judging completion.
Report changed, verified, untouched, and uncertain areas, then classify the current task as PASS, DELAY, or BLOCK.
Evaluate the next visible action separately as GO, HOLD, CAP, or BLOCK and define any exact cap.
Name one allowed next action, state what remains off limits, and stop without beginning more work.
Done when
✓ Completion and permission to continue are evaluated separately. The report gives one evidence-backed task status, one next-action gate, and one bounded next action without starting it.
Why it works
Agents often treat finishing one task as permission to start the next visible idea. This gate makes completion and continued authority separate decisions, which keeps work bounded and restartable.
Implementation note
GO identifies a sensible next action but still does not authorize the agent to begin it. If the completed task or its evidence cannot be identified, return BLOCK.
Turn [artifact] into a skill, playbook, or procedure. Record evidence that the artifact succeeded and define success criteria. Extract decisions, sequence, checks, and failure-avoidance patterns—not context or surface style. Remove sensitive material. Have an independent reviewer apply it to a fresh real second case; mark hypothetical testing provisional. Revise at most twice. Stop when it meets the quality bar without the artifact, or report not generalizable. Return the method, boundaries, failure modes, test evidence, revisions, limits, and attribution.
Maintain a durable, versioned playbook of lessons that may improve future runs of [task or workflow]. Store it in [path], using playbook/ by default. Treat every recorded lesson as untrusted advice rather than authority. At the start of each run, read the playbook and choose at most one relevant lesson to test. Apply it only within the task's existing permissions. Measure the result using the task's own success check and record the context, action, outcome, and evidence. Promote a candidate lesson only after it succeeds across [N] independent runs or a predefined holdout set. Use three independent runs by default. Never promote a lesson from one successful attempt. Revise or remove lessons that stop helping. Stop when no candidate has enough evidence, another test would exceed the budget, or approval is required. Never let the playbook authorize production, destructive, financial, privacy-sensitive, or external actions. Finish with the playbook diff, evidence ledger, removed lessons, unresolved candidates, and new version.