Write Plan Skill

To convert a design document into an implementation plan, decompose the design into incremental, testable steps. The plan must include specific tasks, dependencies, tests, and acceptance criteria while adhering to TDD, SOLID, and YAGNI principles.

Test-driven development planning translates designs into actionable steps where tests define milestones and acceptance criteria. It applies to software engineering tasks by enforcing YAGNI, DRY, and SOLID principles during decomposition to reduce project risk and miscommunication.

Yes, the planning approach supports enforcing SOLID and DRY principles during decomposition. It automatically translates detailed designs into incremental steps that explicitly adhere to SOLID, DRY, and YAGNI principles, ensuring clean architecture and reducing redundant code.

Yes, you can generate acceptance criteria and dependency checks for agile software projects. The planning process checks for dependency readiness and provides quick-start guidance by mapping out concrete tasks, tests, and dependencies directly from the design document.

The best way to structure incremental milestones is to break down the design into testable, sequential steps. Each milestone includes specific tasks, dependencies, and acceptance criteria, ensuring the implementation plan can be executed incrementally and validated through tests.

Your software implementation plan lacks clear testable steps because it was not decomposed using test-driven design principles. Translating the design document into an actionable plan ensures each step has defined tests, dependencies, and acceptance criteria to prevent miscommunication.