writing-plans

To generate a detailed implementation plan, define the feature requirements and use the skill to produce file paths, code snippets, testing procedures, and commit instructions. It ensures adherence to TDD, DRY, and YAGNI principles for smooth task execution.

Task decomposition in software development breaks complex features into bite-sized, actionable steps with explicit file modifications and testing instructions. You need it when implementing multi-step tasks to reduce ambiguity and ensure smooth engineer onboarding.

Yes, you can use an implementation plan to onboard engineers with minimal prior knowledge by providing comprehensive contextualization. The generated plan outlines every file to modify, test to write, and command to run, assuming minimal prior context.

The best way to document file structures and testing procedures is to generate a comprehensive plan that includes explicit file paths, bite-sized tasks, and testing instructions. This approach ensures all necessary development details are explicitly outlined.

Yes, this planning approach enforces TDD, DRY, and YAGNI principles during task execution. The generated plans provide specific testing procedures and coding instructions designed to ensure adherence to these core software development principles.