prd-to-issues

Name: prd-to-issues
Availability: InStock
Author: Zesh

Convert PRDs into dependency-ordered GitHub issues with vertical slices.

Updated Aug 23, 2026

Search Tags:#planning #github #backlog #issues #prd #vertical-slices #tracer-bullets

Ready to run

npx skills add https://github.com/zeshone/doc-architect-agent --skill prd-to-issues-zeshone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/zeshone/doc-architect-agent/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/zeshone/doc-architect-agent --skill prd-to-issues-zeshone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.

Core Features & Use Cases

Draft vertical slices that cover end-to-end paths through API, UI, and data layers.
Order slices by dependencies and mark HITL/AFK where appropriate.
Provide an issue body template for each slice and guide dependency-based creation in GitHub.

Quick Start

Provide a PRD URL or number to begin drafting vertical slices and convert them into GitHub issues in dependency order.

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 GitHub issues?▼

To convert a PRD into GitHub issues, provide the PRD URL or number to draft tracer-bullet vertical slices covering end-to-end paths through API, UI, and data layers, then generate each slice as an issue body template. Output is a structured backlog.

What are vertical slices in backlog planning?▼

Vertical slices in backlog planning are independently-grabbable implementation tickets that cover end-to-end paths through API, UI, and data layers. They enable engineers to grab self-contained units of work that deliver functionality across multiple disciplines.

How do I structure a backlog with dependencies using tracer bullets?▼

Structure a backlog with tracer bullets by ordering vertical slices based on their dependencies and marking Human-in-the-Loop (HITL) or Away-From-Keyboard (AFK) steps where appropriate. This guides dependency-based issue creation in GitHub.

Can I generate GitHub issues spanning multiple engineering disciplines from one PRD?▼

Yes, this process is designed for converting a PRD into a structured backlog that spans multiple engineering disciplines. It drafts vertical slices covering API, UI, and data layers, providing an issue body template for each slice.

What is the best way to order GitHub issues created from a PRD?▼

The best way to order GitHub issues created from a PRD is by dependency order. The process orders vertical slices by their dependencies and generates an issue body template for each, guiding dependency-based creation within GitHub.

Do I need a PRD URL to start drafting GitHub issues?▼

Yes, you need to provide a PRD URL or number to begin drafting vertical slices. This input allows the system to break the PRD down into independently-grabbable GitHub issues ordered by dependencies.