writing-plans

To create an implementation plan with zero context, you define task decomposition, file modifications, tests, and commit steps from a spec, outputting a structured document to the docs/plans directory.

The best way to structure TDD-aligned implementation plans is to enforce DRY and YAGNI principles, mapping each task to specific file changes and test paths before coding begins.

You decompose requirements into exact file changes and commit steps by breaking down the spec into sequential tasks, specifying path modifications, test files, and commits for each component.

Yes, you can generate documentation-ready plan files under docs/plans with structured checkpoints, ensuring all files, tests, and commits are defined even when requirements are unclear.

Yes, this planning approach works for multi-file tasks without existing context by applying structured templates that guide development from initial requirements through testing and documentation.

Enforcing DRY and YAGNI principles during task decomposition prevents code duplication and unnecessary features, ensuring the implementation plan remains focused and maintainable across multiple files.