writing-plans

To create an implementation plan from a software specification, you map multi-step tasks to specific files, tests, and documentation, ensuring the output is a self-contained document with bite-sized tasks for zero-context engineers.

Task decomposition in agile software engineering is breaking down multi-file requirements into bite-sized, actionable steps. It maps each step to code, tests, and frequent commits to ensure thorough and self-contained implementation.

You generate a plan document for multi-file code changes by structuring the specification into task sections with file mappings and version-control steps. The plan is saved as a structured markdown file in the docs directory.

Generating implementation plans does not require a specific project format, but it assumes an agile software-engineering context. It outputs a structured markdown plan document into a designated docs path for multi-step tasks.

The best way to document code tasks for developers with no context is to create a comprehensive plan detailing which files to touch, how to test, and what docs to check. This approach applies DRY, YAGNI, and TDD principles to bite-sized tasks.

You should use a structured plan document before coding when facing multi-file, multi-step software tasks. It ensures thorough task decomposition and version-control steps, preventing oversights for engineers lacking prior codebase context.