cy-create-tasks

To break down a PRD or TechSpec into actionable tasks, you provide the document in your workspace to trigger decomposition into granular, independently implementable task files enriched with codebase context and test integration planning.

Generating code-informed tasks from technical specifications involves mapping requirements to implementation steps by exploring the codebase, embedding clear acceptance criteria, sequencing work, and referencing relevant ADRs within structured task templates.

Yes, you need an existing PRD or TechSpec document in the workspace. Task generation relies on these documents as input to decompose requirements into executable, code-informed task files ready for review and approval.

Yes, the process generates structured task templates that can be reviewed and approved before execution. This ensures the granular tasks, acceptance criteria, and codebase context align with project requirements before development starts.

Codebase exploration enriches task generation by extracting real implementation context from existing code. This context is injected into task definitions alongside ADR references and test integration planning to ensure tasks are independently implementable.

Automated task generation is best used when a PRD or TechSpec exists and needs rapid breakdown into sequenced, independently implementable tasks. It maps requirements to executable steps with embedded tests, reducing manual effort in complex codebases.