Level 0 Practice: Define Requirements Before Opening the Repository
About 5 minutes
About This Tutorial
Section titled “About This Tutorial”For the concepts and completion standards, first read Codex Levels 0-10.
Starting implementation too early can cause Codex to fill in unconfirmed profile facts or design decisions. At Level 0, keep the repository closed and separate human-owned facts from design questions for Codex.
What You Will Complete
Section titled “What You Will Complete”You will produce a portfolio requirements note. The goal is not the amount of work; it is a reproducible Level 0 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.
I am planning a Next.js personal portfolio site. Do not inspect a repository yet. Organize required pages, content data, accessibility needs, and exclusions. Leave unconfirmed facts as questions instead of guessing.Check: Continue only when Codex can restate the scope and unresolved questions before acting.
Step 2: Practice
Section titled “Step 2: Practice”- List required pages, publishable facts, and out-of-scope features.
- Ask Codex for options and decision criteria, separating confirmed and pending items.
- Have Codex organize the selected decisions as Markdown for
portfolio-requirements.md.
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 note separates confirmed, pending, and out-of-scope items without invented biography or project claims.
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 1 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]