What problem does it solve? Turning a Product Requirements Document into tracked GitHub issues is manual, error-prone work, and keeping issues in sync when the PRD changes is even harder. This Skill automates both initial issue creation and re-synchronization, maintaining bidirectional traceability between the PRD and GitHub. ## Core Features & Use Cases - Initial Issue Creation: Parses a PRD's epics, functional requirements, acceptance criteria, and MoSCoW priorities, then creates labeled epic and story issues via the gh CLI after user confirmation. - Re-Sync Mode: Detects <!-- GH-ISSUE: --> markers in the PRD, diffs PRD content against live GitHub issues, and classifies items as UNCHANGED, NEW, MODIFIED, REMOVED, or CLOSED before applying confirmed changes. - Traceability Markers: Embeds HTML comment markers linking each epic and FR to its GitHub issue number, keeping the PRD as the single source of truth. - Use Case: After drafting a PRD for a new feature, run this Skill to generate one epic issue per epic and one story issue per functional requirement, complete with MoSCoW priority labels and acceptance criteria checklists. ## Quick Start Ask the assistant to convert the PRD in docs/prd/ into GitHub issues with epics and stories using the gh CLI.