writing-plans

To create an implementation plan from a feature spec, you provide the text specification and the skill generates a structured document covering task breakdowns, file mappings, testing steps, and commit guidance for engineers.

Task breakdown for complex features is the process of outlining required files, tests, and milestones before coding begins, producing a reproducible plan that guides a team from tests to deployment.

You can plan test-driven development workflows by generating a plan that encourages test-first thinking, maps out required files and tests, and provides incremental commit guidance for each step.

Yes, this implementation plan approach works for multi-step features by satisfying explicit task breakdowns, file mappings, testing steps, and documentation milestones across code, tests, and docs.

The best way to structure task breakdowns before writing code is to generate an end-to-end implementation plan from your feature spec, mapping out tasks, files, tests, and documentation in a reproducible document.

Yes, you need a complete feature specification described in text to generate a comprehensive implementation plan that accurately guides engineers from tests through to deployment.