fix: reduced token usage, removed parameters from schema that CLIs never seem to use

docs/tools/analyze.md

@@ -60,7 +60,6 @@ This workflow ensures methodical analysis before expert insights, resulting in d
 - `relevant_context`: Methods/functions/classes central to analysis findings
 - `issues_found`: Issues or concerns identified with severity levels
 - `confidence`: Confidence level in analysis completeness (exploring/low/medium/high/certain)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `images`: Visual references for analysis context
 
 **Initial Configuration (used in step 1):**

docs/tools/codereview.md

@@ -75,7 +75,6 @@ The above prompt will simultaneously run two separate `codereview` tools with tw
 - `relevant_context`: Methods/functions/classes central to review findings
 - `issues_found`: Issues identified with severity levels
 - `confidence`: Confidence level in review completeness (exploring/low/medium/high/certain)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `images`: Visual references for review context
 
 **Initial Review Configuration (used in step 1):**

docs/tools/debug.md

@@ -68,7 +68,6 @@ This structured approach ensures Claude performs methodical groundwork before ex
 - `relevant_methods`: Specific methods/functions involved in the issue
 - `hypothesis`: Current best guess about the underlying cause
 - `confidence`: Confidence level in current hypothesis (exploring/low/medium/high/certain)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `continuation_id`: Thread ID for continuing investigations across sessions
 - `images`: Visual debugging materials (error screenshots, logs, etc.)
 

docs/tools/precommit.md

@@ -135,7 +135,6 @@ Use zen and perform a thorough precommit ensuring there aren't any new regressio
 - `relevant_context`: Methods/functions/classes affected by changes
 - `issues_found`: Issues identified with severity levels
 - `precommit_type`: Type of validation to perform (external/internal, default: external - ALWAYS use external unless explicitly told otherwise)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `images`: Screenshots of requirements, design mockups for validation
 
 **Initial Configuration (used in step 1):**

docs/tools/refactor.md

@@ -97,7 +97,6 @@ This results in Claude first performing its own expert analysis, encouraging it
 - `relevant_context`: Methods/functions/classes requiring refactoring
 - `issues_found`: Refactoring opportunities with severity and type
 - `confidence`: Confidence level in analysis completeness (exploring/incomplete/partial/complete)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `hypothesis`: Current assessment of refactoring priorities
 
 **Initial Configuration (used in step 1):**
@@ -198,4 +197,4 @@ Analyzes multiple files together to understand:
 - **Use `refactor`** for: Structural improvements, decomposition, modernization, code organization
 - **Use `codereview`** for: Finding bugs and security issues with immediate fixes
 - **Use `analyze`** for: Understanding code without making change recommendations  
-- **Use `debug`** for: Solving specific runtime issues rather than structural problems
+- **Use `debug`** for: Solving specific runtime issues rather than structural problems

docs/tools/secaudit.md

@@ -82,7 +82,6 @@ security remediation plan using planner
 - `relevant_context`: Methods/functions/classes central to security findings
 - `issues_found`: Security issues identified with severity levels
 - `confidence`: Confidence level in security assessment completeness (exploring/low/medium/high/certain)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 - `images`: Architecture diagrams, security documentation, or visual references
 
 **Initial Security Configuration (used in step 1):**

docs/tools/testgen.md

@@ -66,7 +66,6 @@ Test generation excels with extended reasoning models like Gemini Pro or O3, whi
 - `relevant_files`: Files directly needing tests (required in step 1)
 - `relevant_context`: Methods/functions/classes requiring test coverage
 - `confidence`: Confidence level in test plan completeness (exploring/low/medium/high/certain)
-- `backtrack_from_step`: Step number to backtrack from (for revisions)
 
 **Initial Configuration (used in step 1):**
 - `prompt`: Description of what to test, testing objectives, and specific scope/focus areas (required)
@@ -217,4 +216,4 @@ For UI components and visual elements:
 - **Use `testgen`** for: Creating comprehensive test suites, filling test coverage gaps, testing new features
 - **Use `debug`** for: Diagnosing specific test failures or runtime issues
 - **Use `codereview`** for: Reviewing existing test quality and coverage
-- **Use `analyze`** for: Understanding existing test structure without generating new tests
+- **Use `analyze`** for: Understanding existing test structure without generating new tests