plan-writing

To break down complex software engineering work, divide it into small, independently verifiable steps with clear goals and checkpoints. This structured task breakdown reduces ambiguity for feature work, refactors, or any multi-step projects.

The best way to write a project plan for a feature addition is creating a project-specific structure that defines a clear goal and actionable tasks, each with a verification step. It avoids template-based constraints and saves plans as markdown files in the project root.

Yes, you can use this planning approach for cross-functional product planning. The framework applies to new projects, feature additions, bug fixes, and refactoring across software engineering, product planning, and cross-functional work.

To define verification criteria for task planning, outline actionable tasks where each step includes a specific method to confirm completion. This ensures every small, independently verifiable step has clear goals and checkpoints.

No, you do not need a fixed template for project-scoped plan writing. The framework emphasizes phase-free planning with no fixed templates or global folders, keeping plans project-specific and saving plan files directly in the project root.

During task planning, project plan files are saved as markdown files named with a task slug in the project root directory. This requires a project-scoped plan structure rather than relying on global folders.