writing-plans

To break down a feature into test-driven implementation tasks, you provide the feature description and acceptance criteria. The skill outputs a structured, task-by-task plan that specifies what code to touch, how to test, and how to commit.

Automating task breakdown for multi-step software engineering involves generating a structured plan that enforces task boundaries, tests, and commits. This approach translates specs into actionable work items while preserving a clear audit trail under a standardized documentation location.

Yes, you can save generated implementation plans to a specific directory. The skill enforces saving the dedicated plan document under the standardized `docs/plans` location to maintain a consistent plan structure and a clear audit trail.

Yes, this planning approach enforces test-driven development boundaries. The generated plans explicitly enforce task boundaries, specify required tests for each step, and define commit artifacts to ensure structured, test-driven software engineering.

You need a structured plan document for software development when planning complex tasks from a spec to avoid error-prone manual processes. It is useful when you receive a spec, design, or user story and need a fully documented roadmap with file paths and artifacts before coding.