Generate structured markdown PRDs with problem statements, scope, and acceptance criteria.
npx skills add https://github.com/Dyrean/dotfiles --skill prd-dyrean
Please help me install this Agent Skill. Skill: prd Source: https://github.com/Dyrean/dotfiles/tree/main/opencode/.config/opencode/skills/prd Command: npx skills add https://github.com/Dyrean/dotfiles --skill prd-dyrean
Product teams often struggle to create clear, scoping PRDs that align engineering, design, and product stakeholders. This Skill automates structured PRD generation to reduce time-to-first-review and ensure consistent documentation.
Load the prd skill and request a PRD for a feature named "NewPaymentFlow" to start.
High-intent search queries and answers about installing and using this skill.
To create a structured PRD for RFC reviews, you need a document defining the problem statement, end state, success metrics, acceptance criteria, risks, and technical context to align engineering, design, and product stakeholders.
A PRD to align cross-functional teams should include a clear problem statement, end state, scope, success metrics, acceptance criteria, risks, and detailed technical context to guide feature planning and product migrations.
Generating a markdown PRD file with acceptance criteria and scope involves structuring problem statements, end states, risks, and technical context into a ready-to-submit document named prd-<feature-name>.md in your project root.
Automating PRD generation for feature planning requires a question-driven approach that probes for missing context using targeted clarifying questions, ensuring the final document captures all necessary scope and acceptance criteria.
The best way to draft product requirements for cross-functional alignment is using a standardized PRD structure that explicitly defines success metrics, acceptance criteria, and technical context to reduce time-to-first-review.
Product requirements documents often fail to align stakeholders during RFC reviews when they lack a structured end state, defined acceptance criteria, success metrics, or detailed technical context for the proposed feature.
MomoDavilukeGenerate a structured PRD from conversation context and repository insights.
magozGenerate RFC-ready PRDs with acceptance criteria and save to prd-<feature-name>.md.
OmexITConvert PRD or design docs into epics, tickets, and acceptance criteria.
GabeujinGenerate Product Requirements Documents from Epic descriptions for SaaS features.
