plan-writing

To structure project planning for feature implementation, define the goals, context, approach, and granular tasks. This enforces clear roadmaps and ensures all stakeholders understand the implementation approach before development begins.

Managing task dependencies requires explicitly defining task prerequisites and parallelization opportunities within your workflow. Structured planning maps these relationships out, preventing missed dependencies and inefficient implementation during multi-step work.

Setting verification criteria for task completion requires mandating concrete, evidence-based verification steps. This enforces evidence-based verification before task completion, ensuring success is measured accurately and objectively.

Structured task planning is applicable to risky operations and refactoring. It provides a standardized framework that defines goals and context, ensuring clear roadmaps are established before executing any risky operational changes.

Unstructured task planning leads to missed dependencies because it lacks explicit prerequisite definitions. Without a standardized framework, poorly defined tasks cause confusion and inefficient implementation across the project workflow.