cy-create-tasks

To break down a PRD into actionable tasks, you need a structured task decomposition process that converts PRD requirements and user stories into granular, independently implementable task files. This Skill automates that by generating ready-to-implement tasks enriched with explicit dependencies and test requirements.

Yes, you can generate task files directly from a TechSpec. If a TechSpec is missing entirely, the task breakdown can also be derived directly from PRD requirements and user stories, ensuring structured task generation with implementation context regardless of the available documentation.

Adding codebase context to task files requires exploring the existing codebase to populate Implementation Details, Relevant Files, and Dependent Files sections. This Skill performs codebase-informed enrichment automatically, ensuring task boundaries align with existing rules and ADRs.

Task decomposition works seamlessly with existing Architecture Decision Records by using ADRs to justify design decisions within the generated task files. This ADR-aware guidance ensures traceability between requirements, architectural decisions, and the resulting tasks.

The best way to align task boundaries with codebase rules is through codebase-informed enrichment during task decomposition. This Skill analyzes your codebase to ensure generated task files respect existing ADRs, maintain clear dependencies, and specify required test coverage.

You do not need a TechSpec to decompose requirements. This Skill handles missing TechSpecs by automatically deriving granular, independently executable task files directly from PRD requirements and user stories while maintaining implementation clarity.