prd-to-issues

Convert a PRD into dependency-ordered GitHub issues with vertical slices.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/dgowrie/claude-workflows --skill prd-to-issues-dgowrie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/dgowrie/claude-workflows/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/dgowrie/claude-workflows --skill prd-to-issues-dgowrie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a PRD into independently-grabbable GitHub issues to enable parallel planning and cross-functional delivery.

Core Features & Use Cases

  • End-to-end vertical slices: create thin issues that cover schema, API, UI, and tests.
  • HITL / AFK tagging: designate slices that require human oversight or can be implemented autonomously.
  • Dependency-aware sequencing: order issues so blockers are resolved before dependent work.

Quick Start

Convert a PRD into a set of tracer-bullet 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 break down a PRD into GitHub issues for parallel planning?

Breaking down a PRD into GitHub issues involves converting the document into independent, end-to-end vertical slices that span schema, API, UI, and tests to enable cross-functional delivery.

What is the best way to create vertical slices from a product requirements document?

The best way to create vertical slices from a product requirements document is applying tracer-bullet slicing to generate thin issues that cover schema, API, UI, and tests for cross-functional teams.

Does this PRD to issue conversion method support dependency-aware sequencing?

Dependency-aware sequencing is supported by ordering issues so blockers are resolved before dependent work begins in your GitHub repository.

How do I tag GitHub issues for autonomous work versus human oversight?

Tagging GitHub issues for autonomous work versus human oversight uses HITL and AFK tagging, designating which slices require human intervention or can be implemented independently.

Do I need a specific PRD format to generate dependency-ordered GitHub issues?

A specific PRD format is not required, but you must provide a PRD in context to generate dependency-ordered GitHub issues using the tracer-bullet slicing methodology.