writing-plans

To convert a project spec into an implementation plan, provide the specification to generate a comprehensive, step-by-step plan. This covers exact file paths, tests, documentation, and deterministic commit messages.

To break down engineering tasks with zero codebase context, generate a plan that assumes no prior knowledge. It enforces DRY, YAGNI, and TDD practices while specifying exact file paths and commands.

The best way to generate TDD commit messages and test steps is using a planning process that enforces test-driven development practices. It outputs bite-sized tasks with deterministic commit messages and clear success criteria.

Yes, this implementation plan generator enforces DRY and YAGNI best practices. It assumes zero knowledge of the codebase and integrates these principles directly into the generated task breakdown and documentation.

Yes, you can use this to plan exact file paths and commands for a new feature. The generated plan documents every required file touchpoint, test change, and command execution step needed for implementation.

The task breakdown steps in the generated implementation plan are highly granular, splitting work into bite-sized tasks of two to five minutes each with clear success criteria for every step.