prd-to-issues

To convert a PRD into actionable development issues, the skill parses your Product Requirement Document and slices it vertically across all system layers, generating complete, verifiable markdown issue files in a local directory.

Vertical slicing in issue tracking breaks down a PRD into complete, end-to-end functional units rather than horizontal technical layers, ensuring each generated issue delivers independent, verifiable value for the development team.

Yes, you can review and approve generated issues before they are created. The skill supports manual review, allowing you to validate the vertical slices before outputting the final markdown files into your local issues directory.

The best way to generate a granular task list from a high-level product requirement document is to use an automated parsing tool that creates structured markdown files for each verifiable issue, ensuring development clarity and streamlined execution.

Yes, the generated issue repository supports manual markdown files for project management. The skill creates local markdown files for each issue, maintaining a structured repository that can be manually reviewed and edited.

You should avoid manual PRD breakdown because it risks missing dependencies across system layers. Automating the process ensures each issue is a complete, verifiable vertical slice, preventing fragmented tasks and streamlining the development workflow.