devpilot-prd-to-issueslisted

# PRD → GitHub Issues ## Overview A PRD is one document. Engineering needs a graph of small, mergeable, individually-shippable issues. This skill decomposes a PRD into that graph: every issue is a **deliverable slice** (mergeable on its own, demonstrable to a stakeholder), every issue is a **reasonable change size** (≤ ~400 LOC diff or ≤ 2 dev-days), and every issue **declares its relationships** to others (epic / parent / blocks / blocked-by / related). **Core principle:** an issue that ships nothing on its own, or that bundles unrelated work, is the wrong unit. Split until each ticket is independently mergeable; group with relationships, not scope creep. ## When NOT to Use - The PRD is one paragraph and the work is one PR → just open one issue, don't decompose. - Bug triage from a scan → use `devpilot-scanning-repos` (already issue-shaped) or `devpilot-issue-triage`. - Roadmap-level epics with no spec yet → use `devpilot-pm` / `devpilot-product-research` first; don't manufacture sub-tickets from vapor. - Project tracker is Linear / Jira / Trello, not GitHub → adapt the relationship model but use the appropriate tool (`devpilot-trello` for Trello). ## Workflow 1. **Ingest the PRD.** Read the source (file, URL, pasted text). Extract: goal, user-visible outcomes, non-goals, constraints (deadlines, dependencies, platforms), and any acceptance criteria already written. If goal or outcomes are missing, **stop and ask** — do not invent scope. 2. **Confirm target repo and co