- Improve plan prompt present plan step.

Author: ericdallo

CHANGELOG.md

@@ -3,6 +3,7 @@
 ## Unreleased
 
 - Added missing parameters to `toolCallRejected` where possible.  PR #109
+- Improve plan prompt present plan step.
 
 ## 0.49.0
 

resources/prompts/plan_behavior.md

@@ -15,18 +15,18 @@ NEVER print codeblocks for file changes unless explicitly requested - use the ap
 ### Tools for Planning
 - `eca_read_file`, `eca_grep`, `eca_directory_tree`: Explore codebase
 - `eca_shell_command`: Read-only commands ONLY (forbidden: >, >>, rm, mv, cp, touch, git add/commit/push)
-- `eca_preview_file_change`: Show exact file changes
+- `eca_preview_file_change`: Show exact file changes in your present plan step.
 
 ### Workflow
 1. **Understand** - Analyze what the user wants
 2. **Explore** - Work through different approaches. During exploration:
    - Show code possibilities in markdown blocks with language names
-   - Save preview tool for final decisions
+   - Take your time reasoning for the best solution possible.
    - Think through multiple options freely
 3. **Decide** - Choose the best solution. If multiple good approaches exist and user preference would help, present the options and ask for guidance before continuing.
 4. **Present Plan** - Write comprehensive plan with:
    - Clear summary and step-by-step approach
-   - Embedded preview tool calls for code changes
+   - Call preview tool for file changes when exist.
    - Descriptions of other actions (tests, analysis, etc.)
 
 ### When to Use What for Code
@@ -48,4 +48,4 @@ NEVER print codeblocks for file changes unless explicitly requested - use the ap
 - If preview fails: re-read file and match content exactly
 
 ### Remember
-Plans can involve many activities beyond code changes. Use preview tool (eca_preview_file_change) when showing concrete file modifications, but embed them within your narrative explanation.
+Plans can involve many activities beyond code changes. Use preview tool (eca_preview_file_change) when showing concrete file modifications, but NEVER mentions the preview function/tool name to user, just explain the plan in your narrative calling the tool when appropriate.