Generate a structured Product Requirements Document from a feature concept.
npx skills add https://github.com/suwandre/my-opencode-config --skill prd-suwandre
Please help me install this Agent Skill. Skill: prd Source: https://github.com/suwandre/my-opencode-config/tree/main/skills/prd Command: npx skills add https://github.com/suwandre/my-opencode-config --skill prd-suwandre
PRD generation helps product teams convert vague feature ideas into concrete, testable requirements, reducing ambiguity and aligning stakeholders across disciplines.
Provide a feature prompt and the skill will generate a structured PRD saved to tasks/prd-[feature-name].md.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document from a feature concept, provide a feature prompt and the skill generates a structured PRD with goals, user stories, functional requirements, success metrics, and testable acceptance criteria.
A PRD for software development should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design considerations, Technical Considerations, Success Metrics, and Open Questions to ensure actionable and testable requirements.
To define testable acceptance criteria for user stories, the generated PRD applies clarifying questions to resolve ambiguities early, ensuring each user story has clearly defined and actionable acceptance criteria for stakeholder alignment.
The best way to document non-goals and success metrics for a new feature is to use a structured PRD template, which explicitly separates Non-Goals from Success Metrics to align teams on project scope and measurable expectations.
Yes, you can save a generated PRD as a markdown file for version control tracking. The skill automatically saves the document to tasks/prd-[feature-name].md for easy tracking and stakeholder alignment.
eKoh951Generate structured PRD outlines from feature descriptions and save to markdown files.
jpoleyCreate atomic backlog tasks with measurable acceptance criteria.
TravisLeeeeeeTransform epics into sprint-ready user stories with acceptance criteria.
TechDufusGenerate Product Requirements Documents through interview-driven research and approval workflows.
