dot-ai-prds-get
Skill336 starsChanged 10 months agoMITView on GitHub
Fetch all open GitHub issues from this project that have the 'PRD' label
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
- write-docsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: …
- Distinctive: line 15
Fetch Issues: Use GitHub CLI to get all open issues with PRD label
- Distinctive: line 37
Priority Analysis: If multiple PRDs exist, help identify:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

