prd-to-issues

Convert product requirement documents into dependency-ordered GitHub milestones and issues.

45|7|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/richkuo/rk-skills --skill prd-to-issues-richkuo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/richkuo/rk-skills/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/richkuo/rk-skills --skill prd-to-issues-richkuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of breaking down high-level product requirements into granular, implementation-ready GitHub issues, ensuring that agents have clear, dependency-aware instructions for every task.

Core Features & Use Cases

  • Dependency-Ordered Planning: Automatically derives milestones and issue sequences based on technical dependencies rather than just feature themes.
  • Standardized Execution Blocks: Stamps every issue with mandatory metadata including build models, effort estimation, and Fable planning signals to ensure consistent agent performance.
  • Use Case: When you have a completed Product Requirements Document (PRD) and need to initiate development, this skill generates a full suite of self-sufficient GitHub issues, each with acceptance criteria and risk-based complexity scoring.

Quick Start

Use the prd-to-issues skill to break the current PRD into a complete set of dependency-ordered GitHub issues and milestones.

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 requirement document into GitHub issues?

To convert a PRD into GitHub issues, you use a skill that transforms refined product requirements into dependency-ordered milestones and fully-specified issue tickets, complete with acceptance criteria and execution metadata.

What is the best way to structure GitHub milestones based on technical dependencies?

Structuring GitHub milestones by technical dependencies involves deriving issue sequences from your PRD based on code execution order rather than feature themes, ensuring each task ticket has clear prerequisite instructions for agents.

How do I generate self-sufficient GitHub issues for automated development agents?

Generating self-sufficient GitHub issues for agents requires stamping each ticket with standardized metadata, including build models, effort estimation, and risk-aware complexity scoring derived directly from your PRD.

Can I automate project management by planning GitHub milestones from a PRD?

Yes, you can automate project management planning by processing a completed PRD to automatically output a full suite of GitHub milestones and issues, formatted specifically for standardized issue tracking and execution.

Does this PRD to issues conversion include risk-aware effort estimation?

Yes, the PRD to issues conversion includes risk-aware effort estimation by applying complexity-based scoring and mandatory Fable planning signals to every generated GitHub issue ticket.

What are the limitations of generating GitHub issues from PRDs?

A limitation of generating GitHub issues from PRDs is that it requires an already refined product requirement document; it breaks down existing requirements rather than drafting the initial product strategy or feature ideation.