writing-plans

To create an implementation plan, define the feature scope, list the files to touch, specify tests to write, and map out commits. This skill generates a standardized plan document with task blocks to guide stepwise execution.

Test-driven planning enforces a stepwise workflow by defining tests and execution steps before coding. It structures tasks into blocks detailing file modifications, test requirements, and commits to ensure clear execution.

Document implementation plans by saving them to a consistent location like docs/plans with a date stamp and feature name. This practice ensures easy versioning and traceability for multi-step software engineering tasks.

Yes, you can draft end-to-end implementation plans specifying which files to touch, tests to write, documentation to update, and commits to perform, capturing all context and dependencies before touching code.

Yes, this approach is designed for multi-step tasks, ensuring all context, scope, and dependencies are captured in a comprehensive plan before any code implementation begins.

You should write an implementation plan before touching code when handling multi-step tasks, ensuring comprehensive scope capture, clear execution steps, and standardized documentation for team alignment.