synthesis-code-planning

To plan code tasks, you provide a task description, existing code, and contextual documentation. The process analyzes the task, generates multiple approaches with pros and cons, evaluates them, and yields an implement-ready plan with a final recommendation.

Evaluating architecture trade-offs requires inputting your task description and existing code. The planning process generates at least two approaches, outlines the specific pros and cons of each, and selects the optimal path to ensure maintainability and performance.

Feature development planning should follow a structured approach: analyze the task, generate multiple approaches, evaluate the trade-offs, and select the best one. This yields an implement-ready plan that guides decisions from initial analysis to final selection.

Yes, this code planning approach applies to feature development, refactors, and architecture decisions across languages and projects. You simply supply the relevant task description, existing code, and contextual documentation to generate a tailored implementation plan.

You need three inputs to generate an implement-ready plan: a clear task description, the relevant existing code, and contextual documentation. These inform the analysis and enable the generation of multiple approaches with evaluated trade-offs.

Multi-approach evaluation is designed for complex feature development, refactors, and architecture decisions. If a task is trivial or requires immediate, single-path execution, generating multiple approaches with trade-offs may add unnecessary overhead to the planning process.