skills.rest
avoidthekitchen
avoidthekitchenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd-to-issues

Convert PRDs into numbered implementation issues with tracer-bullet vertical slices.

1|Updated Apr 13, 2026
Search Tags:#prd#issue-tracking#hitl#task-breakdown#vertical-slices#tracer-bullets#afk
One-click install
npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill prd-to-issues-avoidthekitchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/avoidthekitchen/avilingo-v2/tree/main/.agents/skills/prd-to-issues
Command: npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill prd-to-issues-avoidthekitchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a product requirement document (PRD) into a sequenced set of independently-grabbable implementation issues so teams can plan, assign, and deliver work in small vertical slices.

Core Features & Use Cases

  • Tracer-bullet vertical slices: Break the PRD into thin, end-to-end slices that span schema, logic, API, UI, and tests.
  • HITL vs AFK classification: Mark slices that require human decisions (HITL) versus those that can be merged without human intervention (AFK).
  • Structured issue output: Produce numbered issues with blockers, user-story mapping, acceptance criteria, and verification steps for import or manual creation in an issue tracker.
  • Use case: A product manager needs to turn a multi-feature PRD into 12 demoable developer tickets that can be independently implemented and tested.

Quick Start

Use the prd-to-issues skill to convert the provided PRD file into a numbered issues file named issues.md using tracer-bullet vertical slices.

Frequently Asked Questions about prd-to-issues

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

FAQPage Schema
How do I convert a PRD into engineering-ready issues for sprint planning?▼

To convert a PRD into engineering-ready issues, break the document into independently-grabbable implementation tickets using tracer-bullet vertical slices. This produces sequenced issues mapped with user stories, acceptance criteria, and verification steps for sprint planning.

What are tracer-bullet vertical slices in task breakdown?▼

Tracer-bullet vertical slices in task breakdown create thin, end-to-end implementation issues that span schema, logic, API, UI, and tests. This mechanism ensures each slice is demo-ready and can be independently implemented and tested by engineers.

How do I identify blockers and dependencies when breaking down product requirement documents?▼

Breaking down product requirement documents into numbered issue templates automatically identifies blockers and dependencies for each slice. The output maps user stories and verification steps to ensure proper sequencing and unblocked implementation.

What is the difference between HITL and AFK issue classification?▼

HITL (Human-in-the-Loop) and AFK (Away From Keyboard) issue classification marks slices requiring human decisions versus those that can be merged without human intervention. This distinction streamlines task assignment and automated delivery workflows.

Can I generate a numbered issues file from a PRD for issue tracker import?▼

You can generate a numbered issues file, such as issues.md, directly from a PRD. The output contains structured issue templates with type, blockers, acceptance criteria, and target output filenames, ready for manual creation or import into an issue tracker.

Related Skills

Explore More Product & Management Skills→
VictorHueniVictorHueni

spec-prd

Generate Product Requirements Documents from feature specifications and upstream artefacts.

Community
Advanced
darellchua2darellchua2
4

git-issue-updater

Extract commit details and post structured updates to GitHub issues and Jira tickets.

Community
Advanced
raphaelmansraphaelmans

prd-to-issues

Convert PRDs into vertical-slice GitHub issues with dependencies.

Community
Intermediate
xenitV1xenitV1
230

backend-design

Enforce backend design patterns for scalable systems with vertical slice architecture.

Community
Advanced