prds-get

Retrieves open GitHub issues labeled PRD with JSON metadata via the GitHub CLI.

Updated Sep 25, 2025

Search Tags:#GitHub #PRD #issue #categorization #triage #GitHub CLI #PRD label

Ready to run

npx skills add https://github.com/wiggitywhitney/content-manager --skill prds-get

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prds-get
Source: https://github.com/wiggitywhitney/content-manager/tree/main/.claude/skills/prds-get
Command: npx skills add https://github.com/wiggitywhitney/content-manager --skill prds-get

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams surface all open PRD-labeled issues in a GitHub repository, enabling quick discovery, triage, and planning of product requirements.

Core Features & Use Cases

PRD discovery: Retrieve all open issues labeled PRD, including number, title, URL, labels, assignees, and timestamps.
Structured results: Present issues with key metadata and a direct link to the PRD description or file.
Prioritization & categorization: Group PRDs by purpose (Architecture & Infrastructure, User Experience, Developer Experience, AI & Intelligence, Operations & Monitoring, Integration & Extensibility) to assist planning.
Next steps analysis: Suggest what PRD to tackle next based on recency, dependencies, and blockers.

Quick Start

Use the GitHub CLI to fetch issues: gh issue list --label PRD --state open --json number,title,url,labels,assignees,createdAt,updatedAt

Frequently Asked Questions about prds-get

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

FAQPage Schema

How do I retrieve all open PRDs tracked as GitHub issues?▼

To retrieve open PRDs from GitHub issues, you can use the GitHub CLI to query issues labeled PRD, fetching JSON fields like number, title, url, labels, assignees, createdAt, and updatedAt for structured results.

What is the best way to categorize and triage product requirements documents in GitHub?▼

Categorizing and triaging PRDs in GitHub involves retrieving open issues labeled PRD and grouping them by purpose, such as User Experience or Architecture, to assist prioritization and planning based on recency and dependencies.

Do I need the GitHub CLI installed to fetch issues labeled PRD?▼

Yes, fetching issues labeled PRD requires the GitHub CLI (gh) installed to execute queries like 'gh issue list --label PRD --state open' and return structured JSON metadata for product planning.

Can I group GitHub issues by labels for product planning and documentation workflows?▼

Yes, you can group GitHub issues by labels to structure product planning workflows, categorizing open PRD-labeled issues into distinct groups like Developer Experience and Operations to enable quick discovery and next steps analysis.

How does PRD discovery from GitHub issues handle prioritization and blockers?▼

PRD discovery from GitHub issues handles prioritization by analyzing retrieved metadata fields like updatedAt and labels, suggesting what PRD to tackle next based on recency, dependencies, and blockers.

What metadata fields are available when fetching open PRDs from GitHub?▼

When fetching open PRDs from GitHub, the available metadata fields include number, title, url, labels, assignees, createdAt, and updatedAt, which are extracted via JSON to format structured results for triage.