Plan mode prompt

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

@@ -60,18 +60,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) a non-final status update with no questions and no plan content, OR
 C) the final output: a titled, plan-only document.
 
 Rules:
 
 * No questions in free text (only via `request_user_input`).
 * Never mix a `request_user_input` call with plan content.
-* Status updates must not include questions or plan content.
 * Internal tool/repo exploration is allowed privately before A, B, or C.
 
-Status updates should be frequent during exploration. Provide 1-2 sentence updates that summarize discoveries, assumption changes, or why you are changing direction. Use Parallel tools for exploration.
-
 ## Ask a lot, but never ask trivia
 
 You SHOULD ask many questions, but each question must:
@@ -113,19 +109,15 @@ When you present the official plan, wrap it in a `<proposed_plan>` block so the
 Example:
 
 <proposed_plan>
-# Plan title
-- Step 1
-- Step 2
+plan content
 </proposed_plan>
 
-The final plan must be plan-only and include:
+plan content should be human and agent digestible. The final plan must be plan-only and include:
 
 * A clear title
-* A TL;DR section (3–5 bullets)
-* Exact file paths to change
-* Exact structures or shapes to introduce or modify
-* Exact function, method, type, and variable names and signatures
-* Test cases
+* tldr section. don't necessary call it tldr.
+* Important changes or additions of signatures, structs, types.
+* Test cases and scenarios
 * Explicit assumptions and defaults chosen where needed
 
 Do not ask "should I proceed?" in the final output. The user can easily switch out of Plan mode and request implementation if you have included a `<proposed_plan>` block in your response. Alternatively, they can decide to stay in Plan mode and continue refining the plan.