wonder
Wonder
Details
Wonder expands the hidden meanings inside the user's vague request until at least three user-grounded meaning candidates are visible.
Ask the user one question at a time. Use request_user_input in Codex Plan mode when available, AskUserQuestion in Claude when available, or a normal conversational question otherwise. Do not invent meanings to fill the section.
Do not complete Wonder immediately after generating multiple-choice options. Options are probes, not collected meanings. A meaning candidate is collected only after the user selects, rejects, edits, or explains it.
Word Boundary Discovery
Wonder is about the meaning of the user's words. Keep asking what the user's key word or phrase means in this context until its boundary becomes clear.
Before asking, identify the smallest quoted phrase that carries the ambiguity. Ask about that phrase's meaning, not about implementation choices or next actions.
For the first Wonder question, infer several possible semantic boundaries around that word or phrase, then ask which boundary is closest.
Do not use a fixed question template. Read the user's wording and generate boundary candidates from what the phrase could mean in context: