A repeatable workflow begins with a result you can recognise. A good example is: check every internal link on a draft website, fix broken local links, and produce a list of external links that still need a person to review.
Example task: repair local links in a draft website
Before you start
Write the input location, allowed files, commands, expected output, and definition of done. State the limits as actions: 'Do not publish, delete pages, or change text outside links.' Give Codex the project's own test and formatting commands instead of relying on guesses.
The task, inputs, limits, and required result.
The approved tools and commands.
Changed files, test output, and unresolved items.
Follow these steps
Make it small enough to inspect.
Name what Codex may and may not change.
Review the plan and every changed file.
Keep instructions, example, and checks together.
Run the workflow on a branch or copy. Read the plan, inspect the changed files, and run the checks yourself. When the result is correct, save the instructions with the project and include one example of a successful output.
Check your result
- The workflow uses only required access.
- The project tests and formatting checks pass.
- A person can review the complete change.
- Publishing and destructive actions remain outside the first version.
The next run should begin from the same inputs and end with the same checks. If the process needs a hidden explanation from the original author, it is not reusable yet.