writing-plans

To create an implementation plan, outline files, tests, and atomic tasks with clear boundaries, then save the strategy to docs/plans/YYYY-MM-DD-feature-name.md. This ensures repeatable planning for complex features.

Task decomposition breaks requirements into atomic steps with expected outcomes before coding. It is needed for multi-step software tasks to avoid scope creep, miscommunication, and rework across subsystems.

Map out file structures and interfaces by planning comprehensive implementation strategies that coordinate files, tests, and docs across a single subsystem, storing the plan-first workflow deterministically in markdown.

A plan-first workflow works for coordinating multiple subsystems by breaking tasks into atomic steps with standard headers and clear boundaries, ensuring repeatable planning for complex features and subsystem coordination.

The best way to document implementation strategies is outlining tasks, files, tests, and docs into atomic steps, saving the comprehensive plan to a deterministic markdown storage path to prevent scope creep and rework.

Starting coding before planning risks scope creep, miscommunication, and rework. Planning comprehensive implementation strategies first ensures atomic tasks, clear boundaries, and expected outcomes are established.