plan-writing

To break down complex work into actionable verifiable tasks, create a concise task plan file named task-slug.md at your project root. This enforces explicit task naming and validation criteria for clear project management.

Dependency-aware sequencing organizes your project task breakdown by mapping relationships between steps. It ensures multi-step initiatives and refactoring tasks execute in the correct order based on their dependencies.

Writing verifiable completion criteria requires defining explicit validation outcomes for each task in your plan. Document these in a task-slug.md file at the project root to ensure clear feature development tracking.

Yes, this task breakdown approach applies across feature development, refactoring, and multi-step initiatives. It handles dependencies by enforcing explicit task naming and verifiable completion criteria in a concise plan workflow.

The best way to document project management plans is creating a concise task-slug.md file at the project root. This workflow breaks down complex work into actionable tasks with dependency-aware sequencing and validation criteria.