PRD to Issues

Overview

A PRD describes what a feature must do; it is not something a developer or a coding agent can pick up and ship. This skill turns one into a backlog: a handful of GitHub issues that each put working behaviour in front of a user, fit in one pull request, and carry acceptance criteria precise enough to check. Every requirement is traced to an issue, the order of work is stored as real GitHub relationships (sub-issue of the PRD, blocked by its prerequisites), and nothing is created until the user has approved the breakdown.

Instructions

1. Collect the inputs

Ask only for what cannot be looked up: where the PRD is (issue number, file, or pasted text) and which repository receives the issues. Then read the rest from the project:

gh --version                                   # 2.94.0+ has --parent / --blocked-by / --type
gh repo view --json nameWithOwner,hasIssuesEnabled
gh issue view 142 --json number,title,body,comments,labels,milestone,subIssues
gh label list --limit 200 --json name,description
gh api "repos/{owner}/{repo}/milestones" --jq '.[].title'