Break PRDs into dependency-ordered GitHub issues with vertical slices.
npx skills add https://github.com/whyte25/reusables --skill prd-to-issues-whyte25
Please help me install this Agent Skill. Skill: prd-to-issues Source: https://github.com/whyte25/reusables/tree/main/.agents/skills/prd-to-issues Command: npx skills add https://github.com/whyte25/reusables --skill prd-to-issues-whyte25
This Skill turns a PRD into an end-to-end set of independently implementable GitHub issues, so teams can plan and execute without translating requirements into tickets manually.
Ask the Skill to convert your PRD GitHub issue (provide its issue number or URL) into a numbered, HITL/AFK-labeled set of vertical-slice issues and then create them in dependency order.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into GitHub issues, the Skill fetches requirements from a GitHub issue and breaks them into independently implementable vertical-slice tickets. It creates these issues using gh issue create in dependency order with a provided template.
Vertical slices in product execution are thin tracer-bullet tickets that cut across schema, API, UI, and tests rather than horizontal layers. This structure ensures each GitHub issue delivers end-to-end functionality across all integration layers.
To map user stories to GitHub issues, the Skill links each created issue back to relevant PRD user stories and orders creation sequentially. This approach ensures that all "Blocked by" references point to real, already-created issue numbers.
Yes, you can categorize implementation tickets as HITL (Human-in-the-Loop) or AFK (Away From Keyboard) during issue breakdown. This planning distinction marks which GitHub issues require human interaction versus those that can be implemented end-to-end autonomously.
Yes, you need an existing GitHub issue number or URL containing your PRD details. The Skill fetches the PRD content directly from that GitHub issue to draft the vertical-slice implementation tickets.
The best way to plan tracer-bullet vertical slices is to map dependencies first and then generate thin end-to-end tickets. The Skill drafts these slices with HITL/AFK labels and user-story mapping before creating them in dependency order.
ClyptAIBreak plans, specs, or PRDs into GitHub issues with vertical slices.
softsparkDecompose PRDs into GitHub issues with dependency ordering.
RyanJarvAutomate GitHub issue triage, board synchronization, and sprint planning.
dallenpyrahBreak down complex plans into independently actionable issues for project trackers.
