writing-plans

To turn software requirements into an implementation plan, you need a structured approach that breaks features into actionable, file-level steps. This Skill generates execution plans with exact path targeting and saves them under docs/plans for disciplined development.

The best way to break down a multi-step feature request is creating a commit-ready task breakdown with file-by-file guidance. This ensures another engineer can execute the work sequentially without prior context using explicit verification commands.

Test-driven development fits into implementation planning by organizing each task around failing tests, minimal implementation, verification, and commit steps. This enforces a disciplined task sequence where file modifications are validated before proceeding.

This planning approach is not designed for single-file code changes. It applies specifically to multi-step software tasks requiring file-by-file guidance and a disciplined task sequence to maintain scope and traceability across multiple modifications.

Yes, you need to specify exact file paths because this planning process requires exact path targeting. It designates exactly which files to create, modify, and test so the implementation work stays scoped, traceable, and commit-ready.