writing-plans

You generate task-level implementation plans from a spec by breaking down requirements into phased, actionable tasks with clear ownership and dependencies. This structured planning approach ensures engineers have a clear, review-ready blueprint before coding begins.

Phased task decomposition is the process of dividing cross-cutting engineering concerns into staged, actionable tasks. It standardizes planning structure, enforces plan-header formatting, and ensures work remains traceable and aligned with project documentation.

You enforce a standardized plan document structure by applying a plan-header formatting and plan-location discovery process. This governance mechanism includes a built-in plan-review loop to ensure collaborative planning and reproducibility across teams.

Yes, structured planning applies directly to software engineering projects with cross-cutting concerns and documentation needs. It outlines the planning structure, ensures alignment with project docs, and supports staged execution for comprehensive implementation tasks.

To start plan generation, announce your chosen plan location and wait for user confirmation before writing any plan files. This plan-location discovery step ensures the generated documents are saved correctly and aligns with the review loop.

The best way to ensure implementation plans are review-ready and traceable is to apply a structured plan-review loop during generation. This process enforces plan-header formatting and standardizes the blueprint so work remains governed and reproducible.