plan-writing

Task breakdown splits complex implementation work into 5 to 10 concise, specific actions. Each step includes explicit verification criteria and logical sequencing to ensure dependencies are resolved before final validation.

Refactoring plans require logical work sequencing to order tasks correctly, ensuring dependencies are handled and the final validation step is executed last. This keeps implementation focused and easy to review.

Feature development planning involves defining task-specific sequencing with minimal scope and explicit verification criteria for each step. This turns ambiguous work into an actionable plan with clear testing requirements.

Task breakdown planning applies to bug fixes, new project setup, and refactoring. It requires task-specific sequencing, minimal scope, and explicit verification criteria to ensure each action is easily verifiable.

A concise implementation plan should contain 5 to 10 specific steps. It must include clear verification for each step, with the final verification step ordered last to validate the complete work.