plan-writing

To break down complex project tasks into verifiable steps, decompose work into independent, actionable items with explicit dependencies and concrete verification criteria. This enforces project-specific task granularity to improve clarity and speed up delivery.

The best way to write a project plan for bug fixes and refactoring is to create a concise, action-oriented plan with phased planning guidance. Save it as a task-slug.md file at the project root to keep plans organized and verifiable.

Yes, you can use this task planning approach for software engineering and product management. It applies to new projects, feature additions, bug fixes, and refactoring by enforcing clear task breakdowns with independent, verifiable outcomes.

To ensure your task breakdown has clear verification criteria, structure each task to produce independent, verifiable outcomes. The approach enforces concrete verification criteria and explicit dependencies for every small step.

Plan files should be saved at the project root to maintain project organization. This project-root discipline uses dynamically named task-slug.md files to keep structured plans organized and accessible.