writing-plans

To write an implementation plan, you decompose multi-step tasks into actionable steps, map exact files to touch with clear ownership, and outline required tests and documentation updates before starting code.

Task decomposition is breaking down complex engineering projects into step-by-step tasks with explicit file ownership and validation steps. You need it for multi-step features requiring precise mapping of touched files, tests, and documentation.

You map files and documentation by specifying exact files to touch, defining their responsibilities, and planning documentation updates alongside test validation steps within a repeatable implementation plan format.

Yes, implementation planning handles complex feature specs by enforcing detailed task decomposition, explicit file ownership, and structured validation steps to ensure engineers have a complete map before touching code.

The best way to structure an implementation plan is using a repeatable format that enforces step-by-step task decomposition, file and artifact mapping, test planning, and explicit file ownership across the entire project lifecycle.

You should avoid detailed implementation planning for trivial, single-step changes that do not require task decomposition, file mapping, or complex test and documentation validation to execute correctly.