prd-to-issues

Convert product requirements documents into numbered engineering issues with acceptance criteria.

139|15|Updated Apr 14, 2026

Search Tags:#issues #prd #hitl #task-breakdown #vertical-slices #tracer-bullets #afk

Ready to run

npx skills add https://github.com/maiobarbero/my-ai-workflow --skill prd-to-issues-maiobarbero

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/maiobarbero/my-ai-workflow/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/maiobarbero/my-ai-workflow --skill prd-to-issues-maiobarbero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-form PRDs are hard to translate into actionable engineering work; this Skill provides a structured method to convert a PRD into a set of independently-grabbable, verifiable issues so teams can plan, assign, and implement reliably.

Core Features & Use Cases

Vertical-slice issue drafting: Breaks PRD content into tracer-bullet issues that span schema, logic, API, UI, and tests so each item is demoable and testable.
Classification and sequencing: Tags each issue as HITL or AFK, identifies blockers and dependency order, and flags overly coarse slices that need splitting.
Issue output and templates: Produces numbered, dependency-ordered issues using a reusable template with acceptance criteria, verification steps, and PRD references for traceability.

Quick Start

Convert the PRD located at docs/feature-prd.md into a numbered, dependency-ordered issue list and save it to issues/prd-issues.md.

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 engineering issues?▼

To break a PRD into actionable engineering issues, convert the document into numbered, dependency-ordered tickets using vertical slices that span schema, logic, API, UI, and tests. This produces independently-grabbable items for reliable team planning and assignment.

What are vertical-slice issues in task breakdown?▼

Vertical-slice issues are tracer-bullet tickets that span schema, logic, API, UI, and tests so each work item is independently demoable and testable. They provide a structured method to translate long-form PRD content into verifiable engineering tasks.

How do I identify blockers and dependencies when converting a PRD to tickets?▼

Identify blockers and dependencies during PRD conversion by sequencing the generated vertical-slice issues. The process tags each issue as HITL or AFK, establishes dependency order, and flags overly coarse slices that need splitting before implementation.

Does PRD to issue conversion work for repository workflow planning?▼

PRD to issue conversion applies directly to repository workflows where a product requirements document must be converted into implementation tickets and ordered work items. It produces dependency-ordered issues with acceptance criteria and verification steps for development planning.

How do I classify engineering tasks as HITL or AFK during task breakdown?▼

Classify engineering tasks as HITL or AFK during task breakdown by tagging each vertical-slice issue generated from the PRD. This classification distinguishes human-in-the-loop items from automated tasks, establishing clear dependency order and targeted assignment.

What is the best way to ensure issues generated from a PRD are verifiable?▼

The best way to ensure issues generated from a PRD are verifiable is using a reusable template that includes acceptance criteria, verification steps, and PRD references. This provides traceability and confirms each vertical-slice item is demoable and testable.