prd

Generate a markdown PRD with problem, scope, and acceptance criteria.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/lorrandavid/.dotfiles --skill prd-lorrandavid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/lorrandavid/.dotfiles/tree/main/.config/.copilot/skills/prd
Command: npx skills add https://github.com/lorrandavid/.dotfiles --skill prd-lorrandavid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PRD creation process often suffers from ambiguity and misalignment among stakeholders, leading to scope creep and repeated reviews.

Core Features & Use Cases

  • Clarifying questions drive a complete, shared understanding of requirements.
  • Codebase exploration helps identify constraints, dependencies, and design considerations.
  • Generate a markdown PRD named prd-<feature-name>.md at the project root to capture decisions and acceptance criteria.

Quick Start

Describe the feature and its goals, then request a PRD for that feature.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a product requirements document for RFC planning?

To generate a product requirements document for RFC planning, describe your feature goals and request a PRD. The Skill asks clarifying questions, analyzes your codebase for constraints, and outputs a structured markdown file with acceptance criteria and success metrics.

What is the best way to define feature scope and acceptance criteria for stakeholders?

Defining feature scope and acceptance criteria for stakeholders is best achieved by generating a PRD that captures decisions, motivation, and success metrics. This structured document prevents scope creep and aligns stakeholders on the end state.

Does this PRD workflow analyze my codebase for dependencies and constraints?

Yes, this PRD workflow analyzes your codebase to identify patterns, constraints, and dependencies. Codebase exploration ensures the generated requirements document accurately reflects technical design considerations and existing limitations.

Can I use this for feature migrations and refactors, or only new features?

You can use this for feature migrations, refactors, and new features alike. The PRD workflow applies to any RFC planning scenario where defining the end state, scope, and success metrics is required to prevent ambiguity.

How do clarifying questions improve the product requirements document creation process?

Clarifying questions improve the PRD creation process by driving a complete, shared understanding of requirements before drafting begins. This mechanism reduces ambiguity, prevents misalignment among stakeholders, and minimizes repeated reviews.