planning

To create an implementation plan, you must first gather context and clarify ambiguous requirements through targeted questions. This structured planning process ensures alignment by generating a step-by-step, file-specific execution plan that awaits your explicit approval before any code is written.

Requirement analysis for agile feature implementation involves asking targeted clarifying questions to resolve ambiguity. This process ensures you fully understand user needs and compare different implementation approaches, preventing wasted development effort on misaligned features.

Comparing implementation approaches involves evaluating 2-3 distinct strategies with detailed trade-offs, such as choosing between a microservice or monolith architecture. This approach design phase ensures you select the optimal path before generating a detailed task list.

You cannot start coding immediately under this structured planning process. It enforces a strict policy where no code is written without an explicitly approved plan, ensuring that requirement analysis, approach comparison, and task documentation are fully completed first.

You need to plan before you code to prevent wasted development effort. By ensuring requirements are fully understood, approaches are compared, and plans are explicitly approved, you build the right thing and avoid implementing incorrect or misaligned features.

TDD integration relies on an executable implementation plan that defines a step-by-step, file-specific task list for the chosen approach. This detailed plan provides the necessary structure to sequence tests and implementation phases accurately before coding begins.