prd-to-issues

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

7|1|Updated Mar 15, 2026

Search Tags:#workflow #github #issues #prd #product-management #vertical-slices

Ready to run

npx skills add https://github.com/Harmeet10000/skills --skill prd-to-issues-harmeet10000

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/Harmeet10000/skills/tree/main/skills/backend/prd-to-issues
Command: npx skills add https://github.com/Harmeet10000/skills --skill prd-to-issues-harmeet10000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break PRDs into actionable, independently-grabbable GitHub issues using tracer-bullet vertical slices, enabling teams to start work quickly without ambiguity.

Core Features & Use Cases

Break a PRD into tracer-bullet vertical slices that deliver end-to-end coverage across API, data, UI, and tests.
Distinguish HITL and AFK slices and manage their dependencies and sequencing.
Generate ready-to-use GitHub issue templates that reference the parent PRD and capture acceptance criteria, blockers, and user stories.

Quick Start

Provide the PRD number or URL to start drafting tracer-bullet vertical slices and generate 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 GitHub issues for my development team?▼

To convert a PRD into GitHub issues, you provide the PRD number or URL to generate tracer-bullet vertical slices. This creates ready-to-work GitHub issues containing acceptance criteria, blockers, and user stories for automated creation via gh issue create.

What are tracer-bullet vertical slices in product management?▼

Tracer-bullet vertical slices are end-to-end work items spanning schema, API, UI, and tests that deliver complete coverage. They break PRDs into independently-grabbable issues, allowing team members to start work immediately without ambiguity.

How do I manage human-in-the-loop and asynchronous work dependencies when breaking down a PRD?▼

This process distinguishes HITL and AFK slices to manage their dependencies and sequencing effectively. Each generated GitHub issue captures specific blockers and user stories, ensuring clear tracking of manual versus asynchronous tasks throughout the workflow.

Does this PRD conversion workflow require GitHub integration to function?▼

Yes, this workflow relies on GitHub integration to enable automated issue creation using the gh issue create command. It generates well-formed issue blocks with parent PRD references, acceptance criteria, blockers, and user stories for direct repository population.

What is the best way to structure GitHub issues for vertical slice architecture?▼

The best way to structure GitHub issues for vertical slice architecture is generating blocks that reference the parent PRD and capture acceptance criteria, blockers, and user stories. This ensures each slice delivers end-to-end coverage across API, data, UI, and tests.

How do I create ready-to-work issues from a product requirements document?▼

You create ready-to-work issues by providing the PRD number or URL to draft tracer-bullet vertical slices. The output generates GitHub issue templates containing parent PRD references, acceptance criteria, blockers, and user stories for immediate team execution.