writing-plans

To generate an implementation plan from a feature specification, provide the feature name to produce a step-by-step task breakdown saved to docs/plans/YYYY-MM-DD-<feature-name>.md, detailing files to touch, tests, and commits.

Breaking down complex engineering tasks into actionable steps involves applying DRY, YAGNI, and TDD principles to create bite-sized tasks, ensuring clear documentation of files, tests, and commit history guidance within a standardized markdown plan.

Writing-plans supports test-driven development lifecycle scenarios by enforcing TDD principles within the generated plan, explicitly documenting the tests to write alongside the files to touch and commits to make for each task.

Yes, you can use this approach for multiple work-in-progress software features simultaneously, as it generates standardized, independently saved markdown files in the docs/plans directory to track each feature's lifecycle separately.

The generated task documentation follows a standardized markdown format saved to docs/plans/YYYY-MM-DD-<feature-name>.md, containing consistent sections for files to touch, tests, docs, and commit history.

Yes, the generated plan includes commit history guidance, alongside specifying the files to touch, tests to write, and documentation to update for every step of the feature implementation.