prd-to-issues

Convert PRDs into structured GitHub issue plans with HTML review.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Omniloy/agent-skills --skill prd-to-issues-omniloy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/Omniloy/agent-skills/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/Omniloy/agent-skills --skill prd-to-issues-omniloy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the manual overhead of converting a PRD or spec into a clean GitHub delivery plan, so teams can move from requirements to tracked work without inventing scope or formatting each issue by hand.

Core Features & Use Cases

  • Visual planning first: Build a reviewable HTML plan with epics, sub-issues, labels, milestones, and traceable references to the source document.
  • Issue creation with guardrails: After approval, create GitHub epics and sub-issues through the GitHub CLI, with idempotent reruns and safe default dry-run behavior.
  • Structured issue quality: Every sub-issue includes clear functional and technical sections, acceptance criteria, and optional design references.
  • Use case: A product manager shares a PRD and gets an approved implementation plan that engineers can execute directly in GitHub.

Quick Start

Use the prd-to-issues skill to turn the attached PRD into a visual HTML implementation plan and then create the approved GitHub 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 PRD into structured GitHub issues and epics?

To convert a PRD into GitHub issues, the skill generates a visual HTML implementation plan with epics, sub-issues, labels, and milestones. After plan approval, it creates the corresponding GitHub issues using the gh CLI with idempotent execution.

Can I create GitHub milestones and labels from a product specification automatically?

Yes, you can create GitHub milestones and labels from a product specification. The skill parses the PRD to map requirements to a structured manifest, rendering a reviewable plan before writing labels and milestones to GitHub.

Do I need the GitHub CLI to generate an HTML plan from a PRD?

You do not need the GitHub CLI to generate the initial HTML plan from a PRD. The gh CLI is only required during the subsequent issue creation phase to write approved epics, sub-issues, and milestones to your repository.

What is the best way to trace GitHub sub-issues back to source document sections?

The best way to trace sub-issues to source sections is by using a validated manifest schema. The skill maps requirements from the PRD to existing code surfaces and embeds traceable references directly within the generated HTML proposal and issues.

Are GitHub issues created from a PRD safe against duplicate runs?

GitHub issues created from a PRD are safe against duplicate runs due to idempotent creation logic. The skill uses approval gating and safe default dry-run behavior, ensuring reruns do not duplicate epics, sub-issues, or labels.