prd-to-issues

Convert PRDs into GitHub issues with tracer-bullet vertical slices.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fuxiang123/unity-harness --skill prd-to-issues-fuxiang123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/fuxiang123/unity-harness/tree/main/assets/github/skills/prd-to-issues
Command: npx skills add https://github.com/fuxiang123/unity-harness --skill prd-to-issues-fuxiang123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices to enable incremental, end-to-end delivery.

Core Features & Use Cases

  • Converts a high-level PRD into a structured set of small, testable issues that cover UI, API, and data layers.
  • Provides guidelines to mark slices as HITL or AFK, establish blockers, and map user stories to issues.
  • Supports documenting parent PRD references and tracking progress through GitHub Issues.

Quick Start

Create tracer-bullet based issues from your PRD to start implementing end-to-end features.

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?

Tracer-bullet vertical slices are thin, end-to-end implementation paths that cut across UI, API, and data layers. They enable incremental delivery by transforming high-level PRDs into small, testable GitHub issues that document acceptance criteria, blockers, and user stories for continuous progress tracking.

What is the best way to break down a PRD into implementable work items?

Yes, the generated GitHub issues capture parent PRD references and establish blockers to map dependencies. Each issue created from the tracer-bullet vertical slices includes user stories and acceptance criteria to track execution progress directly within GitHub Issues.

Does this PRD to issues workflow support tracking blockers and dependencies?

Yes, the PRD to issues workflow provides guidelines to establish blockers and map user stories to issues. It captures the PRD structure to generate thin, end-to-end slices across UI, API, and data layers while documenting parent PRD references for tracking progress through GitHub Issues.

How do I create end-to-end slices across UI, API, and data layers from a PRD?

You create end-to-end slices by applying tracer-bullet vertical slices to your PRD. This technique captures the PRD structure and generates thin, testable work items that independently touch UI, API, and data layers, marking each slice with acceptance criteria and user stories.