task-generation-mode

To turn a PRD into an actionable task list, analyze the document to extract high-level parent tasks and granular subtasks. This generates a structured hierarchy that guides development work directly from product requirements.

A two-phase planning workflow generates subtasks by breaking down product requirements through checkpoints and guardrails. It validates the extracted tasks before producing a final markdown planning document with mapped files and tests.

Yes, you can map potential files and tests when generating tasks from a PRD. The process outputs a hierarchical task structure that includes optional mappings to relevant files, tests, and documentation artifacts.

The best way to structure development roadmaps from requirements is to apply a two-phase workflow with validation guardrails. This transforms raw requirements into a markdown planning document containing parent tasks and granular subtasks.

You do not need a specific format to generate a markdown planning document from a PRD. The workflow processes standard product requirements and applies validation guardrails to output a structured markdown file with task hierarchies.

Generated development tasks may lack file and test mappings if the optional mapping feature is not utilized. Applying the full two-phase workflow ensures the final markdown planning document includes potential file, test, and artifact mappings.