writing-plans

To generate an implementation plan from software requirements, identify the spec and produce a structured document with a plan header, task breakdown, explicit file paths, and testing steps. This translates requirements into actionable engineering workflows.

The best way to break down multi-step coding tasks is to generate a comprehensive plan that defines a clear task hierarchy, specifies exact file touches, and outlines documentation and commit steps for full traceability across the codebase.

Structure an engineering plan by including a required plan document header and a clear task hierarchy for complex features. Save the complete plan with defined file paths and steps to a docs/plans directory for organized feature development.

Yes, you can include commit messages and version-control steps in your task documentation. The generated plan outlines change management steps to ensure traceability and integrates version control directly into the engineering workflows.

Yes, plan generation works for multi-step tasks by producing step-by-step tasks with explicit file touches, test cases, and documentation notes. It applies comprehensively to multi-step tasks across entire codebases.

A plan document header is needed for requirements breakdown to provide structured metadata and ensure the generated implementation plan follows a clear task hierarchy for complex features. It standardizes the engineering workflows.