task-start

To align requirements before coding, use a task start workflow that applies decision trees and alignment checklists to clarify goals, inputs, outputs, and scope, preventing scope creep. This generates plan documentation to guide execution.

A decision tree-based task depth assessment evaluates task complexity to determine required analysis and workflow. You need it for new feature requests, complex tasks, and multi-file projects where upfront alignment reduces rework.

Create an alignment checklist for multi-file projects by systematically clarifying goals, inputs, outputs, edge cases, dependencies, and scope. This upfront alignment ensures correct direction before development begins.

You should confirm a UI prototype before starting frontend development whenever a frontend task requires visual validation. Triggering UI prototype confirmation ensures design alignment and reduces downstream rework.

Upfront task planning works effectively for both multi-file projects and new feature requests. It applies decision trees and alignment checklists to scale the required analysis, ensuring correct scope regardless of project complexity.

The best way to document task decisions is generating plan documentation or specs during the alignment phase. This records goals, scope, and decisions to guide implementation and track alignment throughout execution.