writing-plans

To generate an implementation plan from a feature specification, provide the high-level spec to produce a structured task list. The output specifies touched files, tests, documentation, and milestones, saving to docs/plans/YYYY-MM-DD-<feature-name>.md for reproducibility.

The best way to break down a software task for TDD and DRY is generating a comprehensive plan that enforces these practices. It outlines specific touched files, tests, and checkpoints to guide clean, reliable code delivery before implementation begins.

You need a multi-step implementation plan when a feature requires a detailed outline of touched files, tests, and milestones before coding. This eliminates ambiguity by ensuring engineers know exactly what to modify and document for reproducible delivery.

Generating a task breakdown does not require existing documentation, but it creates reproducible documentation as output. Plans are systematically saved as markdown files in the docs/plans/ directory to ensure future reference and reproducibility.

You can use a worktree setup when creating an implementation plan, as the generated plan accommodates worktree workflows. It defines the specific files to touch and checkpoints to hit, ensuring isolated development aligns with the structured milestones.