writing-plans

To create an implementation plan, you generate end-to-end task breakdowns with exact file paths, tests, and complete code samples. This ensures new contributors can execute complex feature development without prior context or guesswork.

Task-splitting is breaking down complex feature development into bite-sized, actionable increments. It provides explicit file paths and complete code samples, ensuring new contributors can execute plans without needing prior context.

Yes, you can include TDD guidance within your implementation plan. The plan structure satisfies requirements for consistent task granularity and integrates testing directly into the bite-sized task breakdown.

The best way to draft a design-to-code handoff plan is to generate comprehensive task breakdowns with exact file paths and complete code samples. This eliminates guesswork and ensures new contributors can execute without prior context.

You should avoid detailed implementation plans for simple, single-step code modifications. These plans are designed for complex multi-step features, refactoring, and design-to-code handoffs where bite-sized task granularity is necessary.