writing-plans

To create a detailed implementation plan, you document step-by-step instructions, identify affected files, and outline code review procedures. This ensures a structured approach to breaking down complex engineering tasks into manageable, bite-sized development steps.

Documenting task-by-task steps involves detailing everything required for each phase, including specific file manipulations, testing protocols, and documentation updates. This methodical approach ensures engineers with limited context can understand and execute the coding process effectively.

Breaking down a coding process involves generating a comprehensive plan that outlines requirements from initial setup to final deployment. By detailing each file manipulation and testing step, it promotes clean code practices and ensures manageable execution.

Yes, structured development planning is designed specifically for engineers with limited context. By documenting step-by-step instructions and code review procedures, it provides the necessary clarity to understand requirements and execute multi-step engineering tasks methodically.

When planning a new feature in a dedicated worktree, you should save the generated development documentation to a structured path like `docs/plans/feature-name.md`. This keeps your implementation plans organized and accessible for code review procedures.