Use Planner Strategy to Save Tokens
This page explains how to separate planning from execution so you get better output with less wasted context.
Core idea
Section titled “Core idea”Do not use the same session for every kind of work if the task is large. Split the workflow into:
- Planner / architect mode for analysis and structure
- Execution mode for implementation
This keeps prompts cleaner and helps avoid spending large amounts of context on the wrong kind of work.
Practical pattern
Section titled “Practical pattern”Use planning first when:
Section titled “Use planning first when:”- requirements are unclear
- the task spans many files
- architecture matters
- you want a step-by-step execution plan before changing anything
Use execution directly when:
Section titled “Use execution directly when:”- the change is small and obvious
- the file location is known
- there is little ambiguity
Simple workflow
Section titled “Simple workflow”- Use a planner-style session to define the problem and output a task list
- Save the plan in your project docs or task tracker
- Open or continue an implementation session
- Execute against the plan instead of rethinking everything each time
What this improves
Section titled “What this improves”- lower token waste
- clearer handoff between thinking and doing
- better task decomposition
- less random prompt drift during coding