writing-plans

Implementation plans are generated from a spec by breaking the work into bite-sized tasks that document file touchpoints, testing considerations, required references, and documentation steps. This enforces a task-by-task approach with frequent commits before coding begins.

The best way to break down multi-step engineering projects is using a plan format that encodes a Plan Document Header and bite-sized tasks. This provides clear task scopes, file touchpoints, tests, and documentation layout to guide execution.

Yes, you can plan refactors or new modules by generating end-to-end implementation plans with clear milestones and acceptance criteria. The plan ensures every task is documented, including which files to touch and testing considerations.

The plan format supports TDD workflows by providing a bite-sized task breakdown that aligns with test-driven development. It documents required references and testing considerations for each step before execution.

Implementation plans should be saved to docs/plans/YYYY-MM-DD-<feature-name>.md using the Plan Document Header template. This standardizes the documentation layout and guides the execution of the generated tasks.

Yes, a complete spec or requirements is needed to generate an executable plan. The skill converts the specification into a comprehensive implementation plan covering task scopes, file touchpoints, tests, and version control.