streamline

MANDATORY PREPARATION

Streamlining Analysis

1. Does this add measurable value? If you can't name the specific value, remove it.
2. Can this be combined with another component? Merge overlapping responsibilities.
3. Is this solving a real problem or an imagined one? Remove speculative complexity.
4. Would a simpler alternative work? Prefer simplicity over elegance.

Common Streamlining Targets

• Remove steps that transform data without changing it meaningfully
• Combine sequential steps that could be one prompt
• Eliminate validation steps that duplicate downstream validation

• Merge tools that operate on the same data with different filters
• Remove tools the model never selects (check usage logs)
• Combine read tools with similar signatures

• Remove instructions the model follows by default
• Consolidate redundant constraints
• Shorten few-shot examples to minimum viable length

• Remove config parameters that always use the default
• Hardcode values that never change between environments
• Merge related config into logical groups

Streamlining Report

1. What to remove/simplify — specific component or code
2. Why it's safe — what ensures functionality is preserved
3. Expected impact — latency reduction, cost reduction, or maintainability improvement

Complexity Score

Streamlining Checklist

• Each component justified with concrete value
• Redundant steps identified and marked for removal
• Tool usage logs checked for never-used tools
• Golden test set passes after each simplification
• No safety guardrails, logging, or error handling removed

Recommended Next Step

{{command_prefix}}evaluate

{{command_prefix}}refine

• Remove error handling in the name of simplicity
• Streamline without verifying the golden test set still passes
• Remove logging or observability
• Simplify below the level of correctness
• Remove safety guardrails