prd-to-issues

Convert a Product Requirements Document into individual markdown issue files.

1|Updated Feb 1, 2026

Search Tags:#project planning #task breakdown #issue tracking #PRD #vertical slicing

Ready to run

npx skills add https://github.com/safzanpirani/pi-config --skill prd-to-issues-safzanpirani

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/safzanpirani/pi-config/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/safzanpirani/pi-config --skill prd-to-issues-safzanpirani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables users to convert Product Requirements Documents (PRDs) into detailed, independently-workable issues, simplifying project planning and ensuring every task is well-defined.

Core Features & Use Cases

PRD Parsing: Break down a PRD into smaller, manageable issues.
Issue Generation: Create local markdown files for each issue in the issues/ directory.
User Interaction: Engage with the user to refine issue granularity and dependencies.

Quick Start

Use the prd-to-issues skill to convert your PRD into issues. Provide the PRD file path, and follow the prompts to define and create the issues.

Frequently Asked Questions about prd-to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert a Product Requirements Document into actionable issues for project planning?▼

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.

What is vertical slicing in task breakdown and how does it apply to issue tracking?▼

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.

How do I generate local issue files from a PRD?▼

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.

Can I define issue scope and dependencies when breaking down a PRD?▼

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.

Do I need any external project management tools to parse a PRD and create issues?▼

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.

What are the limitations of using vertical slicing for PRD task breakdown?▼

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.