skills.rest
fray-cloud
fray-cloudCOMMUNITY
Explore all skills by this author →
GitHub

prd-to-issues

Break a PRD into dependency-ordered GitHub issues using tracer-bullet vertical slices.

Updated Mar 23, 2026
Search Tags:#planning#github#issues#prd#project-management#requirements-breakdown#vertical-slices
One-click install
npx skills add https://github.com/fray-cloud/coin --skill prd-to-issues-fray-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/fray-cloud/coin/tree/main/.agents/skills/prd-to-issues
Command: npx skills add https://github.com/fray-cloud/coin --skill prd-to-issues-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. This enables teams to convert a PRD into actionable work items and track progress across implementation.

Core Features & Use Cases

  • Break PRDs into vertical slices that traverse all layers end-to-end, producing complete, testable work items.
  • Distinguish between HITL and AFK slices and manage dependencies to reflect real-world workflows.
  • Generate GitHub issues from the PRD using a consistent template to kick off implementation work.
  • Use cases: convert a PRD to issue tickets, create implementation tickets, or break down a PRD into work items for planning and tracking.

Quick Start

Provide the PRD URL or issue number to begin breaking it into tracer-bullet issues.

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 down a PRD into actionable GitHub issues?▼

To break down a PRD into GitHub issues, you provide the PRD URL or issue number to generate tracer-bullet vertical slices that traverse all layers end-to-end, producing complete and testable work items tracked in GitHub.

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

Tracer-bullet vertical slices are independently-grabbable implementation tasks that traverse all layers end-to-end, producing complete and testable work items from a PRD to reflect real-world workflows and dependencies.

How do I convert a product requirements document into development tickets?▼

Converting a PRD into development tickets involves generating GitHub issues from the document using a consistent template, organizing work items through dependency-ordered, slicer-based tasks for implementation planning.

Can I manage human-in-the-loop and automated workflow dependencies when creating GitHub issues?▼

Yes, when breaking down a PRD, you can distinguish between HITL and AFK slices and manage their dependencies to accurately reflect real-world workflows within the generated GitHub issues.

What is the best way to organize implementation tasks from a PRD for tracking?▼

The best way to organize implementation tasks is using dependency-ordered, slicer-based tasks that generate GitHub issues from a PRD using a consistent template, enabling teams to track progress across implementation.

Related Skills

Explore More Product & Management Skills→
skalanuxskalanux
1

prd-to-issues

Breaks a PRD into dependency-ordered vertical slice engineering issues with HITL/AFK labels.

Community
Intermediate
DigiBanks99DigiBanks99

prd-to-issues

Break PRDs into dependency-ordered GitHub issues via gh issue create.

Community
Advanced
tomholfordtomholford
6

prd-to-issues

Break a PRD into dependency-ordered GitHub issues using vertical slices.

Community
Intermediate
caeziumcaezium
2

prd-to-issues

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

Community
Advanced