prd-to-issues

Convert PRDs into dependency-ordered GitHub issues with tracer-bullet slices.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill prd-to-issues-levezze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/Levezze/devkit/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/Levezze/devkit --skill prd-to-issues-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting a PRD into actionable engineering work is slow and often produces issues that are too broad, too layer-specific, or missing clear dependencies.

Core Features & Use Cases

  • Tracer-bullet vertical slicing: Breaks a PRD into thin issues that cut through schema, API, UI, and tests end-to-end rather than creating horizontal slices by layer.
  • AFK vs HITL planning: Labels slices as implementable-and-mergeable (AFK) or requiring human decisions/reviews (HITL), helping teams manage review bottlenecks.
  • Dependency-aware issue creation: Produces an ordered set of GitHub issues where “Blocked by” references real prior issues, then creates them via the GitHub CLI.

Quick Start

Tell your AI: “Use prd-to-issues to break this PRD into tracer-bullet GitHub issues; the PRD is https://github.com/<org>/<repo>/issues/<number>.”

Frequently Asked Questions about prd-to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into GitHub issues with clear acceptance criteria?

Tracer-bullet vertical slicing is a technique that breaks a PRD into thin, end-to-end issues cutting through schema, API, UI, and tests, rather than creating horizontal layer-specific slices, ensuring each issue delivers独立 functionality.

Can I create GitHub issues in dependency order directly from an existing PRD?

You can start by telling your AI to use the Skill on a specific PRD URL, such as one located via `gh issue view` with comments. It then proposes and iterates on slice granularity before creating the issues.

What is the difference between AFK and HITL labels when planning product requirements?

AFK (Away From Keyboard) labels identify slices that are implementable and mergeable without human intervention, while HITL (Human In The Loop) labels mark issues requiring human decisions or reviews, helping teams manage review bottlenecks.

Does this approach work for converting product requirements into vertical slices instead of horizontal layers?

Yes, the approach specifically converts product requirements into vertical slices that cut end-to-end through the stack, avoiding the common problem of producing broad or layer-specific issues that lack clear dependencies.