writing-plans

To break down complex software features, you need a detailed implementation plan that specifies file modifications, provides code examples, and outlines testing procedures. This ensures large features become small, actionable steps for engineers.

To generate an implementation plan enforcing Test-Driven Development, specify a step-by-step workflow that includes writing failing tests, creating minimal implementation code, and defining commit instructions. This structures development using TDD, DRY, and YAGNI principles.

Creating a software development plan with limited context requires generating detailed task breakdowns with contextual guidance. This approach provides necessary information on files to modify, code snippets, and documentation references to ensure clarity.

Yes, you can use structured task breakdowns for adding user authentication. By generating a step-by-step implementation plan, you outline the exact file modifications, testing procedures, and code examples required to implement the feature efficiently.

Implementation planning helps with documenting file modifications and testing procedures by providing necessary contextual guidance. The generated plan explicitly specifies file changes, includes code examples, and outlines the required testing procedures for the development workflow.

The limitation of generating implementation plans with limited context is that the plan's accuracy depends entirely on the initial task description. While it provides structured file modifications and TDD steps, engineers must still validate the contextual guidance against the actual codebase.