plan-writing

To break down ambiguous work into verifiable tasks, create a plan file at your project root listing 5-7 ordered tasks with explicit outcomes and a final Done When criterion. This simple structure reduces miscommunication by ensuring each task has measurable verification criteria.

Verification-driven planning is a task management approach where each decomposed task includes concrete verification criteria to ensure quality and track progress. It converts vague multi-step workflows into independently verifiable actions with explicit outcomes.

Yes, you can use a structured plan for feature development, refactors, and bug fixes across software projects of varying sizes. The plan structure applies dependency-aware ordering to reveal critical paths and enable parallel work for any multi-step workflow.

Start writing a project plan by creating a concise markdown file at the project root. Save it as a task-slug.md file listing 5-7 tasks ordered by dependency, including project-specific assets when present, to reveal the critical path and enable parallel work.

The best way to structure a plan for multi-step workflows is to enforce a simple format with a Goal, verifiable Tasks, and a Done When section. This structure decomposes complex work into small, independently verifiable tasks with explicit outcomes.

You do not need external project management tools to track verifiable tasks. You can write a concise plan directly at the project root as a markdown file, utilizing dependency-aware ordering to manage progress without additional software requirements.