plan-writing

To break down complex work into verifiable tasks, you decompose multi-step projects into 2-5 minute focused outcomes with clear dependencies and concrete verification criteria, reducing ambiguity and miscommunication.

The best way to plan a multi-step feature implementation is to sequence tasks with dependency awareness, creating a compact plan file at the project root that avoids templated structures and enforces project-specific planning principles.

Yes, you can use this task breakdown approach for refactoring projects. It applies to feature implementation, refactors, or any multi-step work requiring careful coordination by guiding task scope and logical ordering.

To verify a planned task is complete, each task in the breakdown includes a concrete way to confirm it is done. This ensures small, focused tasks yield a single, independently verifiable outcome.

No, you do not need any external dependencies to generate project plans. The skill operates independently to produce a compact, verifiable plan file dynamically named and saved at the project root.

You should avoid templated plans for multi-step project work because they lack project-specific planning principles. This approach ensures logical ordering and dependency awareness with a recommended plan structure tailored to your actual work.