work-plan

Defining acceptance criteria for a new software feature involves specifying exact conditions that must be met for completion. This skill facilitates the planning phase by guiding the creation of acceptance criteria, ordered task lists, and documented design decisions.

Documenting design decisions during development planning is best handled by saving design rationale and trade-offs to dedicated markdown files. This enforces structured documentation of architectural choices before implementation begins.

Breaking down implementation tasks into an ordered list requires structuring your development workflow into actionable steps. This skill supports creating ordered task lists and parallelization strategies after initial research is complete.

Specific file naming conventions for development workflow documentation are required for design notes and summary updates. Adhering to these conventions ensures design decisions and task plans are correctly structured within the project management context.

A structured planning approach for software development tasks should be used after research to define exactly what done looks like. It streamlines the planning phase by ensuring clear acceptance criteria and organized task lists before implementation begins.