prd

Generate structured markdown PRDs with problem statements, scope, and acceptance criteria.

Updated Jun 22, 2024

Search Tags:#workflow #planning #documentation #requirements #prd #product-management #rfp

Ready to run

npx skills add https://github.com/Dyrean/dotfiles --skill prd-dyrean

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Structured PRD generation: Produces a markdown PRD with Problem Statement, End State, Scope, Risks, and Acceptance Criteria.
Question-driven clarification: Probes for missing context with targeted clarifying questions.
RFC-ready formatting: Outputs a ready-to-submit PRD file named prd-<feature-name>.md in the project root.

Quick Start

Load the prd skill and request a PRD for a feature named "NewPaymentFlow" to start.

Frequently Asked Questions about prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a structured PRD for RFC reviews and product migrations?▼

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.

What should be included in a PRD to align engineering and product teams?▼

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.

How do I generate a markdown PRD file with acceptance criteria and scope?▼

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.

Can I automate PRD generation for feature planning without missing context?▼

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.

What is the best way to draft product requirements for cross-functional team alignment?▼

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.

Why does my product requirements document fail to align stakeholders during RFC reviews?▼

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.