prd

Generate a Product Requirements Document with problem statements, goals, and success metrics.

42|5|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kazdenc/builder-skills --skill prd-kazdenc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/kazdenc/builder-skills/tree/main/.claude/skills/product/define/prd
Command: npx skills add https://github.com/kazdenc/builder-skills --skill prd-kazdenc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you clearly define product requirements, ensuring everyone understands what needs to be built and the value it delivers, preventing scope creep and misaligned efforts.

Core Features & Use Cases

  • Structured Document Generation: Creates a comprehensive Product Requirements Document (PRD) covering problem statements, goals, user stories, functional and non-functional requirements, and success metrics.
  • Contextual Gathering: Guides you to gather essential context on the problem, audience, and current state before writing.
  • Use Case: When launching a new feature, use this Skill to generate a PRD that outlines the user problem, desired outcomes, and specific requirements for the engineering and design teams.

Quick Start

Use the prd skill to write a product requirements document for the new user profile page.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document for a new feature?

To write a product requirements document, this Skill generates a structured PRD from your context, detailing problem statements, goals, scope, user stories, and functional requirements to align development teams.

What should be included in feature definition to prevent scope creep?

Feature definition should include clear problem statements, desired outcomes, specific scope boundaries, user stories, and non-functional requirements to prevent scope creep and misaligned team efforts.

What's the best way to define success metrics for product development?

The best way to define success metrics for product development is to generate a PRD that explicitly outlines measurable goals and desired outcomes alongside functional requirements before engineering begins.

How do I gather context for a PRD before writing requirements?

Gathering context for a PRD involves defining the user problem, target audience, and current product state, which this Skill guides you to collect before generating the final requirements documentation.

Do I need existing documentation to generate a PRD?

You do not need existing documentation to generate a PRD, but providing initial context on the problem, audience, and current state ensures the output accurately reflects your feature definition goals.