Codex handoff prompt.

Codex can move fast. The handoff has to slow down the right things: what not to touch, what done means, and what proof must exist before the session stops.

Goal:
Make [specific user-visible outcome] true in the current project.

Boundaries:
Do not touch unrelated projects, unrelated files, credentials, customer data, or external services unless I explicitly approve that step.

Done means:
I can open [exact page/file/app path] and see [specific result].

Proof required:
Show the command output, rendered page, public URL, receipt, test result, or screenshot that proves the outcome.

Before final reply:
Tell me what changed, what you verified, what remains unproven, and the one next step.

Why this matters.

The expensive failure is not that Codex makes a mistake. The expensive failure is when the handoff is vague enough that nobody notices the mistake until later.

Use the free generator to turn this into a custom prompt, or buy the full checklist if you want the review questions and red flags too.