writing-plans

To generate an implementation plan from a spec, you create a structured plan artifact with a mandatory frontmatter header, detailing tasks, precise file paths, tests, and commit steps. This reduces ambiguity and rework by turning specs into bite-sized, actionable steps.

Task decomposition in implementation planning involves breaking down multi-step software requirements into explicit, bite-sized tasks. Each task defines specific files, steps, tests, and commit guidelines to ensure traceable progress and enforce separation of concerns before coding begins.

You structure multi-step software tasks by following a strict plan document format that includes a frontmatter header and detailed task sections. Each section specifies precise file paths, required tests, and commit steps to guide development and ensure traceability across projects.

Writing-plans supports DRY and YAGNI principles by guiding task decomposition to enforce separation of concerns and avoid overhead. It saves these structured plan documents to a consistent docs/plans directory using a standardized naming convention for on-demand loading.

You should avoid using a structured implementation plan for highly simple, single-step modifications that do not require task decomposition or risk awareness. Generating a formal plan artifact with frontmatter and commit steps introduces unnecessary overhead for trivial code updates.