This is my current @OpenAI Codex workflow.
It's insanely powerful, and allows Codex to implement far more complex features than the default setup.
It's also much more reliable and leads to better code, with significantly less scope creep.
Follow it exactly (models and all). The results are amazing:
Start by using this prompt (fill in your feature description), with gpt-5 high:
---
# Initial Explanation Stage
Your task is NOT to implement this yet, but to fully understand and prepare.
Here is exactly what I need implemented:
```[DETAILED FEATURE DESCRIPTION HERE]```
--
Your responsibilities:
- Analyze and understand the existing codebase thoroughly.
- Determine exactly how this feature integrates, including dependencies, structure, edge cases (within reason, don't go overboard), and constraints.
- Clearly identify anything unclear or ambiguous in my description or the current implementation.
- List clearly all questions or ambiguities you need clarified.
Remember, your job is not to implement (yet). Just exploring, planning, and then asking me questions to ensure all ambiguities are covered. We will go back and forth until you have no further questions. Do NOT assume any requirements or scope beyond explicitly described details.
---
Once you've answered all of GPT-5's questions and it has nothing more to ask, paste in this prompt:
---
# Plan Creation Stage
Based on our full exchange, now, produce a markdown plan document (`https://t.co/D3A6TySWHM`).
Requirements for the plan:
- Include clear, minimal, concise steps.
- Track the status of each step using these emojis:
- 🟩 Done
- 🟨 In Progress
- 🟥 To Do
- Include dynamic tracking of overall progress percentage (at top).
- Do NOT add extra scope or unnecessary complexity beyond explicitly clarified details.
- Steps should be modular, elegant, minimal, and integrate seamlessly within the existing codebase.
Markdown Template Example:
```https://t.co/D3A6TySWHM (example)
# (Example) Feature Implementation Plan
**Overall Progress:** `0%`
## Tasks:
- [ ] 🟥 **Step 1: Setup authentication module**
- [ ] 🟥 Create authentication service class
- [ ] 🟥 Implement JWT token handling
- [ ] 🟥 Connect service to existing database schema
- [ ] 🟥 **Step 2: Develop frontend login UI**
- [ ] 🟥 Design login page component (React)
- [ ] 🟥 Integrate component with auth endpoints
- [ ] 🟥 Add form validation and error handling
- [ ] 🟥 **Step 3: Add user session management**
- [ ] 🟥 Set up session cookies securely
- [ ] 🟥 Implement session renewal logic
- [ ] 🟥 Handle session expiry and logout process
...
```
Again, for clarity, it's still not time to build yet. Just write the clear plan document. No extra complexity or extra scope beyond what we discussed. The plan should lead to simple, elegant, minimal code that does the job perfectly.
---
Now, once this plan is done, look it over, and if it looks good, switch the model to gpt-5-codex high, then prompt it with:
---
Now implement precisely as planned, in full.
Implementation Requirements:
- Write elegant, minimal, modular code.
- Adhere strictly to existing code patterns, conventions, and best practices.
- Include thorough, clear comments/documentation within the code.
- As you implement each step:
- Update the markdown tracking document with emoji status and overall progress percentage dynamically.
---
