prd-to-backlog-v3

Convert a PRD into GitHub issues on the TI project board.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill prd-to-backlog-v3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-backlog-v3
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/prd-to-backlog-v3
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill prd-to-backlog-v3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a PRD, Screen Inventory, and Decisions Log into a milestoned backlog of vertical-slice stories and automate the creation of GitHub issues on the TI project board, following TI story-writing standards.

Core Features & Use Cases

  • Decompose PRD into vertical-slice milestones and stories that map to delivery phases.
  • Create GitHub issues on the project board aligned to TI story-writing standards.
  • Read and apply TI standards, including backlog sizing and issue ordering, to ensure consistent planning.
  • Support optional inputs like Screen Inventory and Decisions Log to enrich stories and traceability.

Quick Start

Provide the path to your PRD and, optionally, paths for the screen inventory and decisions log to begin generating a prioritized backlog.

Frequently Asked Questions about prd-to-backlog-v3

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

FAQPage Schema
How do I convert a PRD into GitHub issues for my project board?

Decomposing a PRD into backlog stories means breaking a product requirements document into vertical-slice milestones and issues. This Skill maps delivery phases to structured stories, creating ready-to-work GitHub issues on your project board.

Do I need a screen inventory and decisions log to generate backlog stories from a PRD?

A screen inventory and decisions log are optional inputs for generating backlog stories from a PRD. Providing them enriches the vertical-slice stories and improves traceability, but the Skill can decompose a PRD using just the PRD path.

How to decompose a PRD into vertical-slice milestones for delivery?

To decompose a PRD into vertical-slice milestones, provide the PRD path to trigger stage-0 context loading. The Skill applies deterministic decomposition rules and milestone-based story ordering to output foundation, milestone, and story issues ready for review.

Can I automate story-writing standards when creating GitHub issues from a PRD?

You can automate story-writing standards when creating GitHub issues from a PRD. This Skill reads and applies TI story-writing standards, ensuring consistent planning by following backlog sizing and issue ordering rules during issue creation.

What are the limitations of using a PRD to generate GitHub issues automatically?

A limitation of generating GitHub issues from a PRD automatically is that the Skill outputs issues without implementation. It strictly performs deterministic planning and decomposition into foundation, milestone, and story issues, leaving development work to the team.