prd-to-issues

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

2|Updated Apr 25, 2026

Search Tags:#workflow #prd #project-management #github-issues #vertical-slices #tracer-bullets

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

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

Break PRDs into end-to-end vertical slices that map to implementation tasks across API, UI, and data layers.
Generate GitHub issues in dependency order with blockers and user-story mapping.
Facilitate collaborative scoping and validation through HITL/AFK cutovers and a structured PRD-to-issues workflow.

Quick Start

Draft tracer-bullet vertical slices from the PRD and create 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 break a PRD into GitHub issues for sprint planning?▼

Break a PRD into GitHub issues by decomposing product requirements into end-to-end vertical slices. These tracer-bullet slices map implementation tasks across API, UI, and data layers, generating trackable issues with proper blocking dependencies.

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

Tracer-bullet vertical slices are end-to-end implementation paths through API, UI, and data layers that divide a PRD into independently-grabbable tasks. They map product requirements into trackable GitHub issues with user-story mapping and blocking dependencies.

How do I generate GitHub issues in dependency order from a product requirements document?▼

Generate GitHub issues in dependency order by decomposing the PRD into vertical slices and categorizing each as HITL or AFK. This structured workflow outputs templated issues with proper blocking dependencies to prevent bottlenecks.

Can I use vertical slices to distribute work across teams from a single PRD?▼

Yes, vertical slices distribute work across teams by breaking a PRD into independently-grabbable GitHub issues. Each slice maps an end-to-end implementation path, allowing parallel development while maintaining structured dependency tracking.

Do I need to categorize PRD slices before generating GitHub issues?▼

Yes, categorize PRD slices as HITL (human-in-the-loop) or AFK (away-from-keyboard) before generating GitHub issues. This cutover validation facilitates collaborative scoping and ensures the templated issues map correctly to implementation tasks.