Generate structured PRDs with acceptance criteria and success metrics.
npx skills add https://github.com/Khoiwall/be_vidify --skill prd-khoiwall
Please help me install this Agent Skill. Skill: prd Source: https://github.com/Khoiwall/be_vidify/tree/main/.opencode/skill/prd Command: npx skills add https://github.com/Khoiwall/be_vidify --skill prd-khoiwall
PRD Creation Skill helps teams translate ideas into formal, actionable requirements that guide engineering, design, and product decisions, reducing ambiguity and rework.
Create a complete PRD with Problem Statement, Proposed Solution, End State, and Acceptance Criteria, and save it to the project root or under .beads/artifacts/<bead-id>/prd.md if a bead ID exists.
High-intent search queries and answers about installing and using this skill.
A product requirements document defines the end state of a feature using structured sections for the proposed solution, acceptance criteria, success metrics, and constraints. This translates ideas into machine-ready specifications to align cross-functional teams.
A PRD for RFC reviews needs a Problem Statement, Proposed Solution, End State, Acceptance Criteria, and Metrics. It must also include a Tasks section for execution to guide engineering, design, and product decisions while reducing rework.
Machine-readable PRD specifications are generated by defining the feature end state, acceptance criteria, and proposed solution details. The output is saved as a markdown file in the project root or under a specific artifacts directory for cross-functional alignment.
PRDs align engineers, designers, and product owners by providing a shared, machine-readable specification for migrations and refactors. They define the end state, constraints, and success metrics to ensure stakeholders agree on scope and execution tasks.
During beaded workflows, PRD artifacts are saved as markdown files under the .beads/artifacts/<bead-id>/ directory. When no bead ID exists, the file is placed in the project root or named using the specific feature name for easy access.
korchasaGenerate a Product Requirements Document through a structured question and answer process.
DarkCodePEGenerate linked PRD, SPEC, ADR, and TASK artifacts for new features.
DyreanGenerate structured markdown PRDs with problem statements, scope, and acceptance criteria.
KuassGenerate structured Product Requirements Documents with acceptance criteria and machine-convertible tasks.
