How do I install the Dot AI Prds Get skill?

Run npx skillmds add vfarcic/dot-ai-prds-get in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dot AI Prds Get skill do?

Fetch all open GitHub issues from this project that have the 'PRD' label It is listed under Product & Planning on SkillMD.

Is Dot AI Prds Get safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dot AI Prds Get?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dot AI Prds Get free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dot AI Prds Get?

vfarcic (@vfarcic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dot AI Prds Get by vfarcic — Agent Skill

Name: Dot AI Prds Get
Rating: 4.2 (5 reviews)
Author: vfarcic

File contents

Get All PRDs

Fetch all open GitHub issues from this project that have the 'PRD' label.

Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/

Process

Fetch Issues: Use GitHub CLI to get all open issues with 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.

---name: dot-ai-prds-getdescription: Fetch all open GitHub issues from this project that have the 'PRD' label---# Get All PRDsFetch all open GitHub issues from this project that have the 'PRD' label.**Note**: If any `gh` command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/## Process1. **Fetch Issues**: Use GitHub CLI to get all open issues with 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 clarification5. **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 PRDsThis provides a complete view of all active product requirements and helps with project planning and prioritization.

Frequently asked questions