writing-plans

To generate an implementation plan, provide your existing spec or requirements to create a structured task breakdown. The plan outlines touched files, code structure, tests, and verification criteria before you begin coding.

Task breakdown divides a multi-step feature into bite-sized coding tasks to enforce DRY, YAGNI, and TDD principles. You need it when starting a new feature that requires structured pre-coding guidance and detailed documentation.

Create an implementation plan by feeding your feature spec into the planner, which structures the work into bite-sized tasks. This enforces DRY, YAGNI, and TDD principles by detailing specific steps, artifacts, and verification criteria.

Yes, this implementation plan generator works directly with your existing specs or requirements. It uses them as the input to produce a comprehensive end-to-end plan with a task-by-task breakdown.

Generated implementation plans are saved as markdown files in the docs/plans directory. They use a date-based filename format, specifically docs/plans/YYYY-MM-DD-<feature-name>.md, ensuring chronological organization.

A software implementation plan should include touched files, code structure, tests, and documentation. It provides bite-sized tasks and verification criteria to ensure structured pre-coding guidance and adherence to engineering principles.