slow-is-fast

To plan code modifications effectively, use a research-plan-code workflow that grounds every decision in evidence. This approach enforces structured phases, risk assessment, and explicit decision documentation prior to making code changes.

An evidence-based workflow automates research, planning, and coding phases to ensure cross-functional validation. It applies abductive reasoning and documented decision records within the execution context for moderate and larger tasks.

Assess risks before modifying code by enforcing a structured planning sequence that evaluates alternatives and collects relevant evidence. This provides traceable reasoning and cross-checking prior to implementation.

You need a structured research and planning workflow for moderate and complex tasks that require thorough exploration. It ensures traceable reasoning and cross-functional validation before you implement code changes.

This research-plan-code approach is designed for moderate and larger tasks requiring thorough exploration and cross-checking. Small bug fixes do not typically require the enforced structured phases and explicit decision documentation it provides.

The best way to document decisions during code modification planning is to enforce explicit decision records within the execution context. This grounds every choice in evidence and provides traceable reasoning through abductive logic.