prd-to-issues

Break a PRD into vertical slice issue drafts with acceptance criteria.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill prd-to-issues-canepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/Canepro/codex-skills/tree/main/skills/prd-to-issues
Command: npx skills add https://github.com/Canepro/codex-skills --skill prd-to-issues-canepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a PRD into a backlog of small, independently valuable implementation issues organized by vertical slices.

Core Features & Use Cases

  • Breaks a PRD into vertical slices aligned to product boundaries
  • Generates concrete issue drafts with scope, acceptance criteria, and dependencies
  • Supports optional GitHub issue creation for direct integration

Quick Start

Provide the PRD and let the tool generate a prioritized set of issue drafts ready for ingestion.

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 shippable backlog issues?

To break a PRD into shippable backlog issues, the tool analyzes your PRD and target codebase to identify modules and boundaries, producing end-to-end vertical slices with clear acceptance criteria.

What are vertical slices in issue drafting and why use them?

Vertical slices in issue drafting are small, independently valuable implementation units organized by product boundaries. They ensure each generated issue delivers end-to-end functionality rather than isolated technical components.

Can I generate GitHub issues directly from a PRD?

Yes, you can generate GitHub issues directly from a PRD. The tool produces ready-to-use issue drafts and can optionally create GitHub issues or Markdown templates for direct ingestion if requested.

Does the issue generation work without connecting a codebase?

Analyzing a target codebase helps identify integration points to produce accurate vertical slices, but you can simply provide the PRD to generate a prioritized set of issue drafts ready for ingestion.

What is the best way to organize backlog dependencies from a PRD?

The best way to organize backlog dependencies from a PRD is to generate concrete issue drafts that explicitly map scope, acceptance criteria, and dependencies aligned to your product boundaries.

When should I not use vertical slices for issue drafting?

You should not use vertical slices for issue drafting when your PRD targets a completely greenfield project without an existing codebase to analyze for modules, boundaries, and integration points.