prd-to-issues

Convert PRD documents into GitHub epics and story issues using the gh CLI.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill prd-to-issues-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/prd-to-issues
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill prd-to-issues-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about prd-to-issues

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

FAQPage Schema
How do I convert a PRD into GitHub issues?

Place the PRD in docs/prd/, ensure the gh CLI is authenticated, then run the conversion workflow. It parses epics and functional requirements, shows a summary table for confirmation, and creates labeled epic and story issues via gh issue create.

How to sync GitHub issues when a PRD changes?

Re-sync mode reads the GH-ISSUE HTML comment markers embedded in the PRD, fetches each issue's current state with gh issue view, and diffs the content. It presents a classification table (NEW, MODIFIED, REMOVED, CLOSED) and only applies changes you explicitly confirm.

Does this work without the GitHub CLI installed?

No, the gh CLI is a hard prerequisite and must be authenticated via gh auth status. The workflow never calls the GitHub API directly or uses curl; all issue operations go through gh commands.

What labels are created for PRD-based issues?

Seven labels are created idempotently with the --force flag: epic, story, and task for issue types, plus must-have, should-have, could-have, and wont-have for MoSCoW prioritization. Re-running label setup never fails.

Will it automatically update issues without my approval?

No, re-sync changes are never auto-applied. The workflow always presents a diff summary table and asks which actions to apply, and issue creation also requires confirmation of the parsed summary table first.