Level 1 Practice: Read the Repository and Produce a Change Plan
About This Tutorial
This tutorial organizes the scope, deliverable, and completion checks for repository work delegated to Codex.
General advice cannot prove that a change fits the repository routing, design system, or checks. At Level 1, inspect real files as evidence without editing them.
What You Will Complete
You will produce a related-file map and change plan. The goal is not the amount of work; it is a reproducible Level 1 delegation boundary and completion check.
Step 1: Set the Boundary
Before handing work to Codex, state the goal, scope, exclusions, and completion criteria. Adapt this prompt to your project.
Do not edit yet. Investigate the files related to portfolio rendering. Report each file path, its role, existing patterns, likely change points, and validation commands.Check: Continue only when Codex can restate the scope and unresolved questions before acting.
Step 2: Practice
- Ask Codex to read the Level 0 requirements and repository instruction files.
- Identify entry points for pages, components, data, styles, and tests.
- Summarize files to change, files to preserve, and required checks.
Keep the scope stable and inspect the output or diff after each stage.
Step 3: Verify Completion
You are done when every plan item cites a real path and clearly distinguishes verified facts from assumptions.
Record the actions performed, supporting evidence, and anything not verified. Also record why work stopped when a condition was not met.
Troubleshooting
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
Replace vague criteria such as “implement it” with observable files, commands, pages, or review results.
Next Step
Continue to Level 2 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]