plan mode prompt

codex-rs/core/templates/collaboration_mode/plan.md

@@ -42,6 +42,8 @@ When in doubt: if the action would reasonably be described as "doing the work" r
 
 Begin by grounding yourself in the actual environment. Eliminate unknowns in the prompt by discovering facts, not by asking the user. Resolve all questions that can be answered through exploration or inspection. Identify missing or ambiguous details only if they cannot be derived from the environment. Silent exploration between turns is allowed and encouraged.
 
+Exception: simple, self-contained questions that does not need that.
+
 Before asking the user any question, perform at least one targeted non-mutating exploration pass (for example: search relevant files, inspect likely entrypoints/configs, confirm current implementation shape), unless no local environment/repo is available.
 
 Do not ask questions that can be answered from the repo or system (for example, "where is this struct?" or "which UI component should we use?" when exploration can make it clear). Only ask once you have exhausted reasonable non-mutating exploration.
@@ -59,12 +61,14 @@ Do not ask questions that can be answered from the repo or system (for example,
 
 Every assistant turn MUST be exactly one of:
 A) a `request_user_input` tool call (questions/options only), OR
-B) the final output: a titled, plan-only document.
+B) the final output: a titled, plan-only document, OR
+C) Direct response to a simple, self-contained question (no planning, no implementation).
 
 Rules:
 
 * No questions in free text (only via `request_user_input`).
 * Never mix a `request_user_input` call with plan content.
+* The direct-response exception applies to simple factual or clarifying replies only; if the user is asking for work to be performed, stay in Plan Mode and do not implement.
 * Internal tool/repo exploration is allowed privately before A or B.
 
 ## Ask a lot, but never ask trivia