...
npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prds-get
Please help me install this Agent Skill. Skill: dot-ai-prds-get Source: https://github.com/vfarcic/dot-ai-website/tree/main/.claude/skills/dot-ai-prds-get Command: npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prds-get
This Skill helps product managers and engineers quickly identify and understand all active Product Requirement Documents (PRDs) for a project, streamlining prioritization and planning.
Fetch all open PRDs from this project.
High-intent search queries and answers about installing and using this skill.
To fetch PRDs from GitHub issues, you can use a tool that queries your repository for open issues labeled 'PRD' via the GitHub CLI. This aggregates all active Product Requirement Documents, presenting their metadata and categorizing them by functional area to streamline project planning.
Organizing GitHub issues for product management is done by retrieving open issues labeled 'PRD' and grouping them into meaningful categories like Architecture, UX, and AI. This provides a consolidated view of upcoming features and their current status for roadmap adjustments.
Yes, you need the GitHub CLI installed to retrieve project PRDs from issue tracking. The skill requires the GitHub CLI to query issues within the current project repository, fetch detailed metadata like creation dates, and present prioritization insights.
The best way to categorize product requirement documents in GitHub is to extract open issues labeled 'PRD' and sort them into functional groups such as Architecture, UX, and AI. This approach helps identify dependencies, recency, and potential blockers for sprint planning.
Yes, you can get actionable next steps for prioritization from your GitHub PRDs. After fetching and organizing the issues, the skill analyzes dependencies, recency, and potential blockers to suggest concrete actions for project planning and roadmap adjustments.
When fetching GitHub issues labeled as PRD, the extracted metadata includes the issue number, title, creation date, update date, assignees, and direct links. This detailed information helps product managers quickly understand the status of each requirement.
erclxClassify open GitHub feedback issues into direct fixes, plan-worthy features, or clarification requests.
YougLin-devEvaluate research findings and update prd.json with logged changes.
yocxy2Convert vague product requirements into structured GitHub issues and development worktrees.
rito528Parse GitHub issue content and apply status labels via the GitHub API.
