writing-plans

Task breakdown transforms vague requirements into discrete, verifiable steps with explicit dependencies and verification checkpoints. It identifies what to do, in what order, and how to confirm completion before implementation begins, preventing missed work and blocking issues.

An implementation plan for multi-file work must map task dependencies, list affected files, specify verification criteria, and include risk assessment. This structure ensures tasks execute in order, dependencies are visible upfront, and each step is testable before proceeding.

Dependency mapping prevents out-of-order task execution and mid-implementation blocking. Identifying which tasks must complete first eliminates surprises, allows parallel work where possible, and ensures the plan is executable without rework or delays.

A written plan is required for projects with 3+ distinct steps, cross-file work, multiple dependencies, or explicit verification needs. It applies when brainstormed concepts need structure before execution, eliminating guesswork and ensuring stakeholder approval on approach.

Task planning is designed for projects with 3+ distinct steps and cross-file or cross-system work. Small, single-file changes typically don't require formal breakdown; use it for larger features where dependencies and verification checkpoints matter.