Generate structured PRDs from feature descriptions and save them to specs/prds.
npx skills add https://github.com/rogvid/dotfiles --skill prd-rogvid
Please help me install this Agent Skill. Skill: prd Source: https://github.com/rogvid/dotfiles/tree/main/opencode/.config/opencode/skill/prd Command: npx skills add https://github.com/rogvid/dotfiles --skill prd-rogvid
Planning and scoping for new features can be vague and error-prone. This Skill generates structured, actionable Product Requirements Documents (PRDs) from a feature description to align teams and reduce rework.
Provide a feature description and it will generate and save a complete PRD to specs/prds/[seq]-[status]-[feature-name].md.
High-intent search queries and answers about installing and using this skill.
To generate a PRD, provide a feature description. The Skill asks clarifying questions to resolve ambiguity, then produces a complete document with goals, user stories, and acceptance criteria, saving it to specs/prds.
A structured product requirements document includes Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, Non-Goals, Design and Technical Considerations, Success Metrics, and Open Questions.
Writing user stories with acceptance criteria is handled by providing a feature description. The Skill scopes the feature by generating structured user stories and mapping specific acceptance criteria to each requirement.
Yes, you can automate product launch documentation. The Skill generates the PRD and saves the output automatically as a markdown file in specs/prds using a kebab-case naming convention.
Yes, the PRD generator asks clarifying questions after receiving the initial feature description. This resolves ambiguity and ensures the final product requirements document aligns with team expectations.
The best way to document non-goals and open questions is to generate a structured PRD. This confines project scope by explicitly listing non-goals and tracking open questions for product planning alignment.
thepriceisrightGenerate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.
quockidangAssess requirement documents for technical design and coding readiness.
AbsolutelySkilledGenerate user stories and acceptance criteria using INVEST and Given/When/Then templates.
harrymunroGenerate a structured PRD with goals, user stories, and success metrics.
