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.