prd-to-issues

Convert PRDs into tracer-bullet GitHub issues with HITL or AFK types.

2|Updated Mar 24, 2026

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

Ready to run

npx skills add https://github.com/AmbitionsXXXV/Etyon --skill prd-to-issues-ambitionsxxxv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/AmbitionsXXXV/Etyon/tree/main/.agents/skills/prd-to-issues
Command: npx skills add https://github.com/AmbitionsXXXV/Etyon --skill prd-to-issues-ambitionsxxxv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices to enable precise implementation planning.

Core Features & Use Cases

Break PRDs into tracer-bullet vertical slices that cover end-to-end across all layers (schema, API, UI, tests).
Classify slices as HITL or AFK and define blockers and user stories coverage.
Use case: convert a PRD into a set of actionable GitHub issues ready for coordinated development.

Quick Start

Give me the PRD's GitHub issue number or URL and I'll generate a tracer-bullet breakdown into actionable 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 development?▼

To break down a PRD into GitHub issues, you provide the PRD's issue number or URL to generate a tracer-bullet breakdown of actionable items. This process organizes product requirements into independently-grabbable vertical slices covering schema, API, UI, and tests.

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

Tracer-bullet vertical slices are deterministic, end-to-end work items that cut across all project layers including schema, API, UI, and tests. This slicing technique enables precise implementation planning by creating independently-grabbable issues for coordinated development.

Can I convert product requirements into implementable work items for projects of varying sizes?▼

Yes, you can convert product requirements into implementable work items for projects of varying sizes. The breakdown supports creating deterministic, end-to-end slices with structured GitHub issue formats ready for creation and coordinated development.

How do I generate actionable GitHub issues from a PRD URL?▼

You generate actionable GitHub issues by supplying the PRD's GitHub issue URL. The system then parses the requirements and outputs a structured GitHub issue format, classifying slices as HITL or AFK and defining blockers and user stories coverage.

Does the generated GitHub issue format include blockers and user stories coverage?▼

Yes, the generated GitHub issue format includes blockers and user stories coverage. It classifies the tracer-bullet vertical slices as HITL or AFK types and defines these elements to ensure the issues are ready for coordinated development.

What is the best way to slice product requirements across code, tests, and UI?▼

The best way to slice product requirements across code, tests, and UI is using tracer-bullet vertical slices. This approach creates deterministic, end-to-end slices that cover all layers, ensuring each generated GitHub issue is independently-grabbable and ready for implementation.