thinking-controllisted

# Thinking Depth Control Calibrate reasoning effort to the task at hand. Deep thinking is powerful but expensive - both in tokens and latency. ## Thinking Levels ### Minimal Thinking **When:** Routine, mechanical tasks with clear instructions. - Running a command the user specified - Making a simple edit the user described exactly - Reading a file the user pointed to - Formatting or reorganizing existing content **Approach:** Act immediately. Avoid deliberating on obvious actions. ### Light Thinking **When:** Standard development tasks with clear patterns. - Writing a function with clear inputs/outputs - Fixing a straightforward bug - Adding a test for existing behavior - Implementing a well-defined feature **Approach:** Brief consideration of approach, then execute. One pass is usually sufficient. ### Moderate Thinking **When:** Tasks requiring analysis or multi-step planning. - Refactoring code for better structure - Debugging an issue with multiple possible causes - Implementing a feature that touches several files - Writing code that must handle edge cases **Approach:** Consider 2-3 approaches before choosing. Read relevant code first. Plan execution steps. ### Deep Thinking **When:** Complex tasks requiring careful reasoning. - Architecture decisions with long-term implications - Security-sensitive code (auth, crypto, input validation) - Performance-critical algorithms - Resolving conflicting requirements - Understanding unfamiliar or complex codebases **Approa