Module · Codex Engineer
Prompting Codex Well
The anatomy of a request, the context it needs, and what to do when it goes wrong.
TOPIC 01
The Anatomy of a Request
Goal, context, constraints - and the context you can leave out.
What you'll practice
- Write the Three Parts of a Request — guided · beginner
- Curate the Context — practice · intermediate
A command you'll meet
cat ~/codex/prompts/anatomy.mdA request is read once, by a system that has never met you. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Write the Three Parts of a Request
Goal, context, constraints. Every request that works has all three. Write the anatomy down.
Curate the Context
Too much context blurs the task and too little makes it guess. Write the rules for choosing what goes in.
TOPIC 02
Iterating
The second prompt is usually better than the first - and sometimes you need the fourth.
What you'll practice
- Iterate a Request Instead of Restarting — practice · intermediate
- Read a Failed Run — challenge · advanced
A command you'll meet
cat ~/codex/prompts/iterating.mdThe first run is a draft, not an answer. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Iterate a Request Instead of Restarting
When a run goes wrong, the fix is usually a correction, not a fresh start. Write the iteration rules.
Read a Failed Run
A run that failed still produced information. Write the postmortem for the run itself, not just for the code.