writing-plans

To create an implementation plan, describe your multi-step feature. The plan breaks work into bite-sized tasks specifying exact files to touch, tests, docs, and verification steps following TDD principles. This ensures an engineer with zero codebase context can execute successfully.

Task splitting decomposes complex features into bite-sized tasks with clear goals and checkpoints. It documents required files, testing procedures, and commit steps, ensuring engineers without codebase context can execute multi-step software implementations independently.

Yes, implementation planning follows TDD principles by suggesting explicit tests for each task alongside code and documentation requirements. It structures work into frequent commits with verification steps, ensuring test-driven development throughout the feature implementation.

Yes, you can use this for refactoring existing code or adding complex features. It generates end-to-end implementation plans covering files, tests, docs, and verification steps, breaking the work into bite-sized tasks with clear goals and checkpoints.

The best way to document implementation tasks is creating comprehensive plans specifying exact files to touch, code, testing, and docs to check. Break work into bite-sized tasks with clear goals, following DRY, YAGNI, and TDD principles with frequent commits.

You need a task-level implementation plan when starting a coding project, refactoring, or adding complex features requiring explicit files, tests, docs, and verification steps. It ensures engineers with zero codebase context can execute multi-step implementations accurately.