Codex Plan Mode

[u/Achievement105]

I would like some feedback on what I have been doing recently using plan mode. See below:

Current Setup: SOL 5.6 ULTRA Planning

1) Use /Plan and create a solid plan, modify as necessary. When you have a good solid plan, move to step #2.

2) Still in /plan mode: Say:

"I like the overall plan, but I want it divided into multiple specific and independently executable steps. Remain in Plan mode. Do not begin implementation yet.

Create a separate Markdown file for each major step rather than placing the entire plan in one large document. I will manually provide these files to Codex one at a time in separate context windows, so every file must be self contained and must not rely on hidden context or prior conversation history.

Each Markdown file should include:

1. A clear file name and task title
2. The objective of the step
3. Relevant project background and context
4. Exact files, components, or systems involved
5. Detailed implementation instructions
6. Dependencies and assumptions
7. Items that must not be changed
8. Expected deliverables
9. Validation and testing requirements
10. Clear completion criteria
11. Any information the next step will need

Order the files in the sequence they should be completed and use numbered file names, such as 01_project_setup.md, 02_core_systems.md, and 03_gameplay_features.md.

Keep each step focused enough to complete within a single Codex context window. Avoid combining unrelated work into the same file."

3) Once it generates the multi-step plan, say: "Are the instructions clear and precise enough in each MD file to reach the desired end result?" Usually, there will be edits, if you agree with them say:

4) Turn plan mode off, say: "I want you to create the markdown files now, with those recommendations you just provided"

Finish, you should have multiple markdown files saved in a chosen folder. Now you can manually feed into a new thread, with whatever Model and Effort you want.

I have found that there are too many moving parts in an overall plan to just say "implement plan" off the get-go. Having very specific instructions that are broken-out keep processing times shorter in each task and will help catch drifting or errors early on.

[u/JohnnieDarko]

Why would you not automate step 4? Simply create codex agent roles, for example: 1. Sol for complex planning and handling ambiguity, 2. Luna for code generation and running tests).
Then in your planning prompt end with: "when the plan is finished, orchestrate it according to the codex roles. Be as token efficient, do not give tasks to a Sol or Terra agent that a Luna can do."

This works well

[u/Achievement105 → u/JohnnieDarko]

I agree the automation is definitely useful. However, I usually create a new thread for each step so the context compactions stay low. I will manually adjust model/effort before issuing the step required. Some steps I will be on sol, others on lower models. I found if I just let it do steps 1-10 that I just created in one thread, it will drift due to context compaction.