writing-plans

An implementation plan breaks down a spec into required files, tests, docs, and milestones. It outlines steps using DRY and TDD principles, producing a reusable Markdown plan with exact file paths and commands for multi-step software tasks.

Planning multi-step software tasks involves detailing required files, tests, docs, and milestones from a spec. This ensures clear responsibilities and documentation by outlining steps with exact file paths and commands, keeping DRY and TDD principles.

Yes, you can apply TDD and DRY principles when structuring a feature plan by outlining test cases and minimal code changes. The plan breaks features into tasks and commits with exact paths, producing a reproducible Markdown document.

Yes, you need an existing specification to generate a project implementation plan. The process applies to projects where a spec exists but codebase context is limited, detailing files, tests, docs, and milestones to satisfy requirements.

You break down a complex feature into tasks and commits by creating a detailed implementation plan from its spec. This plan outlines required files, tests, and milestones, saving the structure to a reusable Markdown document with exact paths.

You should not use a detailed implementation plan when no spec exists or when full codebase context is already available. This approach is designed for projects where a spec exists but codebase context is limited, requiring detailed file and milestone outlining.