Codex for Real Work: From a Messy Folder to a Clear Handover

Give the folder a specific output

The input is a bounded fictional website project, not an open-ended drive cleanup. A brief describes the intended work, a decision log preserves changes, and an asset inventory exposes missing pieces. The requested result is a useful handover in both human-readable Markdown and structured JSON. Naming those outputs makes it easier to judge whether the agent preserved the important information.

Preserve decisions and dependencies

A later decision can change the scope without erasing the original context. Follow the source before adding an item to a launch checklist, and keep deferred features out of the immediate plan. Missing assets and blocked dependencies need an owner and a next action. Otherwise, a tidy summary can make unfinished work look as though someone has already resolved it.

Use structure to check the document

The episode shows the actual Codex output and reports 22 independent artifact and provenance checks. Structured fields make recurring questions easier to inspect: does the owner exist, is the date retained, and does the status agree with its source? A readable handover still matters because the next person must understand the decision, not only pass a parser.

Keep document checks in their proper scope

These checks concern the handover and its sources. They do not test the fictional website’s behavior or approve its release. A page described as rendered should retain that status until a relevant behavioral check exists. The workflow is useful when it makes the next decision clearer and gives the next owner enough evidence to take it.

Jump to a chapter