Repository navigation
Description
What variant of Codex are you using?
App
What feature would you like to see?
Problem
When users ask Codex to build something, the request often contains important but unstated requirements—especially for UI, games, interactions, animations, visual design, and user experience.
Codex may reasonably fill in those gaps based on common patterns, but the result can still be fundamentally different from what the user intended.
The user then has to discover the mismatches only after seeing the generated result and spend additional turns correcting them.
This creates a loop:
Prompt → Codex guesses missing requirements → implementation → user discovers mismatch → repeated corrections
The problem is not necessarily coding quality. It is missing product/design context before implementation begins.
Use case
For example, a user might say:
“Build a cute physics-based game with a little ball.”
The user may have very specific ideas about:
- visual style
- proportions
- color mood
- animation feel
- physics behavior
- interaction feedback
- UI style
But they may not know how to express all of these requirements in a prompt.
Suggested direction
Before starting implementation, Codex could optionally analyze the request and identify missing information that is likely to materially affect the final result.
Instead of asking everything, Codex should ask only the highest-impact clarification questions.
For example:
“Before I start, I see 3 decisions that could significantly affect the result:
- Should the ball feel soft and cartoon-like or physically realistic?
- Should the UI be minimal or game-like?
- Should the physics feel realistic or intentionally soft/slow?”
The user answers these questions, Codex forms a concise confirmed specification, and then begins implementation.
Why this matters
This would allow users who cannot write a perfect prompt to still communicate their actual intent.
It could make Codex less like:
“Give me a prompt and I will generate code.”
and more like:
“Tell me what you want to make. I will help you clarify it, then build it.”
The key is not to make Codex ask more questions.
The key is for Codex to become better at recognizing:
“I don't have enough information to make a good implementation yet, and this particular missing information will significantly affect the result.”
The challenge is not simply that users cannot write good prompts. Sometimes users themselves do not know which details need to be specified until they see the first result. The first generated version helps them discover what they actually care about. Codex could proactively surface these hidden decisions before implementation.
Additional information
The challenge is not simply that users cannot write good prompts. Sometimes users themselves do not know which details need to be specified until they see the first result.
For example, when building a game, a user may have an intuitive sense that the physics feel “too hard,” the visual hierarchy feels wrong, or the colors lack the intended emotion, without knowing how to express those requirements upfront.
The first generated version can help users discover what they actually care about. Codex could proactively identify these hidden decisions and ask targeted clarification questions before implementation, rather than requiring users to discover and communicate every missing requirement through repeated iterations.
The goal is not to make Codex ask more questions, but to help it recognize which unanswered questions are most likely to affect the final result.
Activity
lolpul commentedon Nov 20, 2026
I strongly support this request, particularly the distinction between clarifying what to build and planning how to build it.
I built a small open-source proof of concept for this workflow: Interrogation Mode — Agent Skill (MIT license). It started with Codex and now uses a shared
SKILL.mdformat with installation guidance for several coding agents.The workflow is:
An optional first-class Codex Requirements Interview mode (or an officially supported skill) could integrate well with Plan Mode: the interview resolves what to implement, then Plan Mode addresses how. Importantly, this should remain opt-in and risk-adaptive so small changes are not slowed down by unnecessary questions.
The current community skill is instruction-only, not a technical write lock. A built-in implementation could provide stronger enforcement through native planning/read-only permissions and a clear approval gate. I have not conducted controlled benchmarks of token usage, rework, or task quality, so I am not claiming measured savings yet.
I'd welcome technical feedback from the Codex team and would be happy to help with a repeatable evaluation set or further iteration if this direction is useful.