Paths/Codex Engineer/Planning with Codex / Plan Decomposition
Review a Plan Before the Edits Start
A plan is a claim about what the change will do. Read it the way you would read a pull request - against the codebase it claims to change.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/plans/review.md exists○
- The document lists the questions to ask of a plan○
- The document states what makes a plan get sent back○
02Walkthrough
1 of 4 revealed- 01
Create the plans directory
The review checklist is written once and used for every plan.
mkdir -p ~/codex/plans - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list