task-decomposition

To break down an approved technical specification into actionable tasks, you can decompose the tech-spec and user-spec files to automatically generate individual, validated task files in English while ensuring template compliance and cross-task integration.

Feature breakdown prevents scope creep by decomposing complex technical specifications into small, manageable atomic task files, validating each task individually, and checking for cross-task integration conflicts before user approval.

Parallel validation works by validating generated task files individually and then performing cross-task integration conflict checks, running up to three iterations of validation to ensure reality checks and template compliance before presenting a summary.

Yes, you need an approved tech-spec file and user-spec files as input. The decomposition process reads these approved specifications to generate individual atomic task files, ensuring the output aligns with the validated technical requirements.

Yes, after generating task files from a technical specification, the process validates tasks individually and then checks for cross-task integration conflicts, running up to three validation iterations before presenting a summary for final user approval.