plan-writing

To break down complex project features into actionable tasks, you create a plan file at the project root and outline 5-10 small, time-bound tasks. Each task includes specific verification criteria to independently confirm completion and reduce ambiguity.

The best way to structure a multi-step refactor plan is to enforce task-level granularity and identify task dependencies. This logical sequencing maps the critical path, enabling parallel work where possible across your codebase.

Yes, this planning framework works for new product initiatives and incremental bug fixes. It adapts to any project effort with minimal boilerplate, guiding both new features and refactors by enforcing a lightweight, project-specific workflow model.

To name and save plan files for easy discovery, you create a new file at the project root dynamically named after your specific task. This root-level naming convention ensures plans are immediately accessible within the codebase.

You should use a verifiable task planning workflow to reduce ambiguity and accelerate delivery. Unlike standard task management, it enforces task-level granularity and requires defined verification criteria to confirm completion at the task level.

Yes, you can apply this planning framework to multi-step initiatives across any codebase. It operates with no external dependencies, adapting to your project-specific workflow to organize complex work into verifiable steps.