prd

Generate a structured Product Requirements Document from a feature description.

1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/pianzhu/my-claude-skills --skill prd-pianzhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/pianzhu/my-claude-skills/tree/main/skill-en/prd
Command: npx skills add https://github.com/pianzhu/my-claude-skills --skill prd-pianzhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) from a brief feature description, reducing ambiguity and accelerating alignment across teams.

Core Features & Use Cases

  • Structured PRD generation: Introduces a complete PRD with sections like Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics.
  • Guided questioning: Asks 3-5 clarifying questions to resolve ambiguities before drafting the PRD.
  • Automated artifact generation: Outputs the PRD to /tasks/prd-[feature-name].md for versioning and sharing.

Quick Start

To generate a PRD, give a feature description such as "Add user profiles with role-based access" and ask the skill to produce a ready-to-edit PRD.

Frequently Asked Questions about prd

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

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

Draft a product requirements document by providing a brief feature description, and the skill outputs a structured PRD with sections like Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics to a markdown file.

What should I include in a PRD to align product, design, and engineering teams?

A PRD should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics to clarify acceptance criteria and align product, design, and engineering teams on feature scope.

Can I generate a ready-to-edit PRD from just a feature description?

Yes, you can generate a ready-to-edit PRD from a feature description by answering 3 to 5 clarifying questions that resolve ambiguities before the structured document is drafted and saved automatically.

How does guided questioning improve PRD generation for project planning?

Guided questioning improves PRD generation by asking 3 to 5 clarifying questions upfront, resolving stakeholder ambiguities and ensuring the final feature definition document is comprehensive and actionable.

Where is the generated PRD artifact saved for versioning and sharing?

The generated PRD artifact is saved as a markdown file at /tasks/prd-[feature-name].md, providing a structured output that teams can use for versioning and sharing during project planning.