Vendored from 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
Fetch Issues: Use the forge CLI to list all open issues with the PRD label
gh issue list --label PRD --state open --json number,title,url,labels,assignees,createdAt,updatedAt
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)
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.
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
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.
1---2name: prds-get3description: Fetch all open issues labeled 'PRD' from this project's git forge (GitHub, GitLab, or Forgejo)4---56> 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.78# Get All PRDs910Fetch all open issues labeled 'PRD' from this project's git forge.1112**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.1314## Process15161. **Fetch Issues**: Use the forge CLI to list all open issues with the PRD label17 ```bash18 gh issue list --label PRD --state open --json number,title,url,labels,assignees,createdAt,updatedAt19 ```20212. **Format Results**: Present the issues in a clear, organized format showing:22 - Issue number and title23 - Creation and last update dates 24 - Current assignees (if any)25 - Direct link to the issue26 - PRD file link (if available in issue description)27283. **Meaningful Categorization**: Group PRDs by their actual purpose and impact, not generic labels:29 - **Architecture & Infrastructure**: Core system changes, API designs, major refactors30 - **User Experience**: Features that directly impact how users interact with the system31 - **Developer Experience**: Tools, workflows, testing, documentation that help developers32 - **AI & Intelligence**: Machine learning, AI-powered features, recommendation engines33 - **Operations & Monitoring**: Deployment, scaling, observability, performance34 - **Integration & Extensibility**: Third-party integrations, plugin systems, APIs35 36 Each category should briefly explain what the PRDs in that group will accomplish for users or the system.37384. **Priority Analysis**: If multiple PRDs exist, help identify:39 - Which PRDs are most recently updated or have active discussion40 - Which PRDs have dependencies on other PRDs41 - Which PRDs are foundational vs. incremental improvements42 - Which PRDs might be blocked or need clarification43445. **Next Steps Suggestion**: Based on the PRD list, suggest logical next actions:45 - Which PRD to work on next based on dependencies and impact46 - PRDs that need attention, updates, or clarification47 - Opportunities for parallel work on independent PRDs4849This provides a complete view of all active product requirements and helps with project planning and prioritization.
vtmocanu