cy-create-tasks

Task decomposition from a PRD involves breaking down product requirements and technical specs into detailed, independently implementable task files. This process maps granular tasks to real implementation work, reducing execution ambiguities and minimizing manual team coordination.

Generating task files with explicit dependencies from a TechSpec involves producing a master task list that follows registry-driven type constraints and templates. This ensures task files include explicit dependencies without cycles and embeds required test expectations for valid engineering workflow orchestration.

Task decomposition works with existing codebases by exploring the project structure to populate file paths, related components, and project conventions. This codebase-informed enrichment ensures generated task files accurately reflect integrated components and actual project scaffolding requirements.

You need an existing .compozy/tasks/<name>/ directory containing at least a _prd.md or _techspec.md file before starting task decomposition. This prerequisite ensures the requirements to convert into executable units for implementation planning and execution orchestration are available.

Task decomposition cannot be used to directly create a new PRD or TechSpec. It strictly applies when an existing PRD or TechSpec must be converted into executable units for implementation planning, rejecting any usage for initial document creation or direct code execution.

Task decomposition includes embedded test requirements in generated task files to ensure each independently implementable unit carries its validation expectations. This enforces task governance, ensuring teams execute engineering work with clear test parameters and fewer integration ambiguities.