prd-to-issues

Break PRDs into vertical slice GitHub issues with dependencies and acceptance criteria.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/kvithayathil/agent-resources --skill prd-to-issues-kvithayathil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/kvithayathil/agent-resources/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/kvithayathil/agent-resources --skill prd-to-issues-kvithayathil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually converting product requirement documents (PRDs) into individual GitHub issues is slow, error-prone, and often results in poorly scoped work items with unclear dependencies and missing acceptance criteria.

Core Features & Use Cases

  • Vertical Slice Generation: Breaks PRDs into tracer bullet issues that cut across all integration layers (schema, API, UI, tests) to deliver complete, demoable value increments instead of disjointed horizontal layer tasks.
  • Workflow Classification: Labels each issue as human-in-the-loop (HITL, requiring reviews or architectural decisions) or AFK (implementable without human input) to streamline prioritization and execution planning.
  • Structured Issue Templates: Creates standardized GitHub issues with pre-filled sections for parent PRD reference, acceptance criteria, dependency tracking, and linked user stories to ensure consistency across all generated tickets.
  • Use Case: A product team with a new feature PRD can use this skill to automatically generate a prioritized list of implementation tickets with clear dependencies, eliminating hours of manual ticket drafting and cross-team alignment work.

Quick Start

Use the prd-to-issues skill to break down the PRD in GitHub issue #123 into a set of vertical slice implementation tickets with clear dependencies and acceptance criteria.

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

Breaking a PRD into actionable GitHub issues involves using tracer bullet vertical slice methodology to cut across schema, API, and UI layers, generating discrete implementation tickets with clear dependencies and acceptance criteria.

What is vertical slice implementation in project planning?

Vertical slice implementation is a planning method that generates tracer bullet issues delivering complete, demoable user-facing value increments across all integration layers, avoiding disjointed horizontal layer tasks.

How do I generate GitHub issues with clear dependency tracking from a PRD?

Generating GitHub issues with clear dependency tracking from a PRD requires structured issue templates that pre-fill sections for parent PRD references, acceptance criteria, and linked user stories to ensure consistent work item breakdowns.

Can I classify implementation tickets as human-in-the-loop or AFK during PRD breakdown?

Classifying implementation tickets as human-in-the-loop (HITL) or AFK during PRD breakdown applies workflow labels to distinguish tasks requiring architectural decisions or reviews from those implementable without human input.

Why should I avoid horizontal layer slicing when creating implementation tickets?

Avoiding horizontal layer slicing when creating implementation tickets prevents disjointed tasks by ensuring each generated GitHub issue cuts across schema, API, and UI layers to deliver an end-to-end, demoable value increment.