cy-create-tasks

Decomposing a PRD into actionable tasks involves creating a master _tasks.md and per-task files, enriched with codebase-derived implementation context, explicit dependencies, and embedded tests for each work item.

Codebase-informed task decomposition scans your codebase to locate relevant files and conventions, ensuring each generated task file contains specific integration points and architectural patterns for maintainable implementation.

You can generate traceable task files by inputting your TechSpec; the system enforces a strict template structure that embeds ADR references and test cases directly into each task file for traceability.

Yes, PRD decomposition generates granular, independently implementable work items by ensuring every task file is self-contained with explicit dependencies and embedded tests to prevent integration conflicts.

You need either a PRD or a TechSpec to create codebase-enriched task files. The workflow activates whenever a specification document exists and requires breakdown into executable tasks with implementation context.

Generated task files require embedded tests and explicit dependencies to guarantee traceable, testable, and maintainable work items, allowing developers to execute each self-contained task without breaking existing codebase integration.