prd-to-issues

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

1|Updated May 11, 2026

Search Tags:#prd #hitl #vertical slices #afk #issue planning #product-to-engineering

Ready to run

npx skills add https://github.com/skalanux/puntofiles --skill prd-to-issues-skalanux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/skalanux/puntofiles/tree/main/dot_agents/skills/prd-to-issues
Command: npx skills add https://github.com/skalanux/puntofiles --skill prd-to-issues-skalanux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a PRD into a set of independently implementable issues so teams can plan, execute, and verify work using vertical slices instead of slow, horizontal breakdowns.

Core Features & Use Cases

Tracer-bullet vertical slicing: breaks a PRD into thin end-to-end slices that cut through schema, logic, API, UI, and tests.
HITL vs AFK planning: labels each slice as Human In The Loop (needs review/decision) or Away From Keyboard (can proceed without human interaction).
Dependency-aware issue writing: produces a numbered issue list in dependency order with clear verification steps and acceptance criteria.

Quick Start

Tell the assistant: “Use the tracer-bullet method to break my PRD into numbered HITL/AFK issues and save them to the file I specify, without editing the PRD.”

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

HITL (Human In The Loop) slices require manual review or decisions, while AFK (Away From Keyboard) slices can proceed autonomously without human interaction. Labeling each issue helps teams parallelize work and identify exactly where manual approval is needed.

What is the tracer-bullet method for product-to-engineering issue planning?▼

Yes, the system can optionally assess your existing codebase during the breakdown process. After analyzing the PRD and current code, it drafts slice granularities and quizzes you on the proposed breakdown before writing the final dependency-ordered issue file.

Will converting my PRD into issues modify my original product requirements document?▼

No, converting your PRD into issues will not modify the original document. The system reads the product requirements and writes the generated numbered issue list to a separate output file that you specify during the initial prompt.

Do I need to manually order dependencies when creating vertical slice tickets from a PRD?▼

No, you do not need to manually order dependencies. The system automatically produces a numbered issue list arranged in dependency order, complete with clear verification steps and acceptance criteria for each vertical slice.