prd-to-issues

To convert a Product Requirements Document into actionable issues, you provide the PRD file path to the Skill. It parses the document and uses vertical slicing to break it down into independently workable issues stored as markdown files.

Vertical slicing in task breakdown means structuring each issue so it is independently implementable end-to-end. This approach ensures that every generated issue delivers a standalone piece of value rather than requiring dependencies to merge.

You generate local issue files from a PRD by providing the file path. The Skill then creates individual markdown files for each issue inside an issues directory, streamlining your project planning and tracking setup.

Yes, you can define issue scope and dependencies when breaking down a PRD. The Skill engages with you interactively to refine issue granularity and map dependencies before generating the final markdown files.

No external project management tools are required to parse a PRD and create issues. The Skill operates independently using local scripts to generate markdown files, requiring no external dependencies.

A limitation of using vertical slicing for PRD task breakdown is that it requires user input to accurately define issue scope. Complex dependencies might need manual refinement to ensure each issue remains truly independent.