Generate RFC-ready PRDs with acceptance criteria and save to prd-<feature-name>.md.
npx skills add https://github.com/magoz/.dotfiles --skill prd-magoz
Please help me install this Agent Skill. Skill: prd Source: https://github.com/magoz/.dotfiles/tree/main/opencode/.config/opencode/skill/prd Command: npx skills add https://github.com/magoz/.dotfiles --skill prd-magoz
Product teams often spend hours drafting and aligning PRDs, leading to misaligned expectations and duplicated work across stakeholders.
prd-<feature-name>.md at the project root to standardize documentation and version control.Provide a feature description, goals, and success criteria, and the skill will generate a complete PRD and save it to prd-<feature-name>.md in the project root.
High-intent search queries and answers about installing and using this skill.
To generate a PRD for a feature migration, provide the feature description, goals, and success criteria. The skill creates a comprehensive document defining what to build, acceptance criteria, and risks, saving it as prd-feature-name.md at your project root.
A product requirements document should include what to build, why it matters, constraints, risks, and acceptance criteria. This skill generates RFC-ready templates ensuring alignment across engineering, design, and product stakeholders before implementation.
Yes, you can use this skill to draft RFC-ready PRDs for refactoring projects. It applies PRD creation to planning migrations or refactors, capturing necessary end states, success metrics, and constraints to guide technical reviews.
The best way to standardize product requirements documents is generating consistent templates. This skill automatically outputs prd-feature-name.md to the project root, standardizing documentation and enabling seamless version control across teams.
Yes, the skill saves acceptance criteria and success metrics directly into the project root. It generates a markdown file named prd-<feature-name>.md, ensuring all defined constraints and requirements are version controlled.
Defining feature goals and constraints before implementation prevents misaligned expectations and duplicated work. Generating a clear PRD ensures all stakeholders understand what to build, why it matters, and the required acceptance criteria.
harrymunroGenerate a structured PRD with goals, user stories, and success metrics.
DyreanGenerate structured markdown PRDs with problem statements, scope, and acceptance criteria.
thepriceisrightGenerate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.
vfarcicGenerate GitHub issues and PRD files with milestone-based planning.