writing-plans

To generate a detailed implementation plan, provide your software development task to get step-by-step guidance. The plan outlines specific files to modify, code to write, tests to execute, and commit messages to use, ensuring clarity for engineers with limited context.

Breaking down complex software features into manageable TDD steps involves dividing tasks into small increments suitable for frequent commits. This approach supports TDD, YAGNI, and DRY principles for efficient development workflows by outlining every test to write and command to run.

Yes, structured task breakdown works for adding user authentication without prior context. Generating a comprehensive plan outlines every line of code to implement and every command to run, ensuring a smooth development process for engineers with limited project context.

Implementation planning explicitly supports YAGNI and DRY principles for efficient development workflows. The generated plans structure complex tasks into small, manageable steps suitable for TDD and frequent commits, ensuring developers only build what is necessary without duplication.

A software implementation plan should include comprehensive details like file modifications, code snippets, testing procedures, and commit messages. Providing these specific elements ensures engineers have all necessary context and step-by-step guidance before starting a new feature.