Level 3 Practice: Implement Multiple Pages and Finish Verification
About 5 minutes
About This Tutorial
Section titled “About This Tutorial”For the concepts and completion standards, first read Codex Levels 0-10.
Stopping after implementation leaves type errors and broken links for someone else to discover. Level 3 treats page work and validation as one completion condition.
What You Will Complete
Section titled “What You Will Complete”You will produce page implementation and validation results. The goal is not the amount of work; it is a reproducible Level 3 delegation boundary and completion check.
Step 1: Set the Boundary
Section titled “Step 1: Set the Boundary”Before handing work to Codex, state the goal, scope, exclusions, and completion criteria. Adapt this prompt to your project.
Implement the approved plan and complete the repository-defined checks. Preserve existing UI and routing. If a check fails, investigate the cause and report the result explicitly.Check: Continue only when Codex can restate the scope and unresolved questions before acting.
Step 2: Practice
Section titled “Step 2: Practice”- Implement the Level 1 plan in small stages: shared layout, listings, then details.
- Run applicable existing tests, lint, and type checks after each stage.
- Require a final report listing changed files, passed checks, failures, and unverified items.
Keep the scope stable and inspect the output or diff after each stage.
Step 3: Verify Completion
Section titled “Step 3: Verify Completion”You are done when the report includes the diff scope, commands and results, and any checks that were not run.
Record the actions performed, supporting evidence, and anything not verified. Also record why work stopped when a condition was not met.
Troubleshooting
Section titled “Troubleshooting”Codex exceeded the requested scope
Section titled “Codex exceeded the requested scope”Stop the task and inspect the diff. Add explicit owned files and exclusions to the prompt, then rerun only the approved scope.
Completion is difficult to judge
Section titled “Completion is difficult to judge”Replace vague criteria such as “implement it” with observable files, commands, pages, or review results.
Next Step
Section titled “Next Step”Continue to Level 4 to expand the delegation boundary by one step.
See the references for the external specifications and background sources used on this page.[1][2][3]