# Prds Get

> Fetch all open issues labeled 'PRD' from this project's git forge (GitHub, GitLab, or Forgejo)

- Skill: `vtmocanu/prds-get` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vtmocanu/prds-get`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vtmocanu/prds-get/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: vtmocanu (https://skillmd.com/u/vtmocanu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vtmocanu/prds-get

---


> Vendored from [vfarcic/dot-ai](https://github.com/vfarcic/dot-ai) `shared-prompts/prds-get.md` (MIT, Copyright (c) 2025 Viktor Farcic). Original author: Viktor Farcic.

# Get All PRDs

Fetch all open issues labeled 'PRD' from this project's git forge.

**Forge-agnostic**: The `gh` commands below are GitHub examples. Detect the forge from `git remote get-url origin` and use the matching CLI, mapping each verb to its equivalent: **GitHub** → `gh`; **GitLab** → `glab` (`glab issue list`); **Forgejo/Gitea** → `tea` (`tea issues list`). If the needed CLI is missing, tell the user and link its install page.

## Process

1. **Fetch Issues**: Use the forge CLI to list all open issues with the PRD label
   ```bash
   gh issue list --label PRD --state open --json number,title,url,labels,assignees,createdAt,updatedAt
   ```

2. **Format Results**: Present the issues in a clear, organized format showing:
   - Issue number and title
   - Creation and last update dates  
   - Current assignees (if any)
   - Direct link to the issue
   - PRD file link (if available in issue description)

3. **Meaningful Categorization**: Group PRDs by their actual purpose and impact, not generic labels:
   - **Architecture & Infrastructure**: Core system changes, API designs, major refactors
   - **User Experience**: Features that directly impact how users interact with the system
   - **Developer Experience**: Tools, workflows, testing, documentation that help developers
   - **AI & Intelligence**: Machine learning, AI-powered features, recommendation engines
   - **Operations & Monitoring**: Deployment, scaling, observability, performance
   - **Integration & Extensibility**: Third-party integrations, plugin systems, APIs
   
   Each category should briefly explain what the PRDs in that group will accomplish for users or the system.

4. **Priority Analysis**: If multiple PRDs exist, help identify:
   - Which PRDs are most recently updated or have active discussion
   - Which PRDs have dependencies on other PRDs
   - Which PRDs are foundational vs. incremental improvements
   - Which PRDs might be blocked or need clarification

5. **Next Steps Suggestion**: Based on the PRD list, suggest logical next actions:
   - Which PRD to work on next based on dependencies and impact
   - PRDs that need attention, updates, or clarification
   - Opportunities for parallel work on independent PRDs

This provides a complete view of all active product requirements and helps with project planning and prioritization.