prd-to-backlog-v4

Decompose PRD, Screen Inventory, and Decisions Log into milestoned GitHub issues.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/drdatarulz/TheL10inator --skill prd-to-backlog-v4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-backlog-v4
Source: https://github.com/drdatarulz/TheL10inator/tree/main/.claude/skills/prd-to-backlog-v4
Command: npx skills add https://github.com/drdatarulz/TheL10inator --skill prd-to-backlog-v4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a PRD, Screen Inventory, and Decisions Log into a milestoned backlog of vertical-slice stories, ready to be turned into GitHub issues following TI standards.

Core Features & Use Cases

  • Automatically map input documents to milestones and vertical slices.
  • Create foundation and story issues on the project board with TI-compliant naming and prioritization.
  • Facilitate review by generating milestone markers and organizing stories under them.

Quick Start

Provide the PRD path and optional --screen-inventory and --decisions-log paths to generate a milestoned backlog.

Frequently Asked Questions about prd-to-backlog-v4

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

FAQPage Schema
How do I turn a PRD into a backlog of GitHub issues organized by milestones?

To turn a PRD into a milestoned backlog, provide the PRD path alongside optional screen inventory and decisions log paths. The tool decomposes these documents into vertical-slice stories and automatically creates foundation and story issues on a GitHub project board.

What is a vertical-slice story in project management?

A vertical-slice story is a foundational project management unit that delivers end-to-end functionality. This backlog generation process maps your product requirements and screen inventory directly into these actionable, TI-standard vertical slices.

How do I generate GitHub issues from a product requirements document?

You generate GitHub issues from a product requirements document by feeding the PRD path into this tool. It resolves project board configuration and automatically creates TI-compliant foundation and story issues organized under planned milestones.

Do I need a screen inventory to create a milestoned backlog from a PRD?

A screen inventory is not strictly required to create a milestoned backlog, but providing it alongside the PRD and a decisions log improves accuracy. These documents work together to fully map project requirements into vertical-slice stories.

What's the best way to organize GitHub project board stories by milestones?

The best way to organize GitHub project board stories by milestones is to use a decomposition tool that applies TI standards. It automatically generates milestone markers and structures foundation and story issues under them for streamlined review.

Can I use a decisions log to help define milestones for my project backlog?

Yes, you can use a decisions log to help define milestones for your project backlog. Supplying the decisions log path with your PRD allows the system to extract architectural constraints and directly map them into planned milestone structures.