writing-plans

To convert a feature spec into an implementation plan, provide the written requirements to generate a step-by-step plan. This process breaks down multi-step features into incremental tasks, specifying files to touch, tests to write, and docs to update.

The best way to break down software engineering tasks is generating a structured plan that enforces TDD, DRY, and YAGNI principles. This ensures task granularity drafting defines clear incremental steps with file paths and command examples before coding begins.

Task granularity drafting for multi-step features works by breaking work into clear, incremental steps. It explicitly defines which files to touch, tests to write, documentation to update, and command examples to execute for validating success.

Generating implementation plans does enforce TDD, DRY, and YAGNI principles. It ensures tasks, tests, and documentation are clearly defined before coding begins, guiding engineers through structured execution saved under the docs/plans directory.

You can save generated implementation plans to a specific directory structure. The skill enforces saving the output plan file directly under docs/plans, specifically using the YYYY-MM-DD-<feature-name>.md naming convention for organization.

You need to generate an implementation plan from a spec when tackling multi-step features requiring structured execution. It is necessary when you must define task breakdowns, test strategies, and documentation updates clearly before starting the actual coding phase.