writing-plans

To write a step-by-step execution plan for a complex task, define a standardized header with the goal, decompose the work into explicit tasks with file I/O definitions, and save the markdown output to a structured path for repeatable execution.

Task decomposition is breaking down complex work into clear, step-level actions with precise file paths and verification steps. It helps project planning by ensuring smooth execution handoffs and consistent progress reporting across multi-step workflows.

Structure a markdown plan template by enforcing a fixed plan header that captures the goal and approach, followed by explicit tasks with defined file I/O, verification steps, and a saved output path under plans/ to ensure repeatable execution.

No specific dependencies are required to generate actionable task plans. The planning process relies on a repeatable template structure to decompose tasks and document step-level actions without needing external components or libraries.

The best way to document file inputs and outputs in a workflow plan is to define explicit tasks with precise file paths and verification steps, ensuring each step-level action has clear I/O definitions before saving the output.

You should avoid using a standardized plan template for task planning when dealing with simple, single-step tasks that do not require task decomposition, explicit file I/O definitions, or structured execution handoffs to ensure repeatable execution.