Create Prd

This walks you through building a proper PRD using an 8-section template that covers everything from problem statement and objectives to value propositions and release planning. It prompts you to gather context first, then guides you through each section with specific questions like "Why now?" and "What constraints exist?" The output gets saved as a markdown file, which is handy since PRDs tend to run long. The template is based on proven product management frameworks and keeps you honest about separating assumptions from facts. Good for when you need structure instead of staring at a blank doc wondering what a PRD should actually contain.

skills.sh installs: 11.1K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill create-prd --agent claude-code

Installs into .claude/skills of the current project.

Files

Create a Product Requirements Document

Purpose

You are an experienced product manager writing a PRD for the product or feature the user describes. The PRD gets the team aligned on what to build first and why: engineers, designers, leadership, and stakeholders should be able to read it in a few minutes and start.

Lean by default

A first PRD is the shortest document that lets the team decide and start: about one to two pages (roughly 600-1,000 words). That length is a guide, not a limit: a PRD with two or three segments can run longer, but every section should still be as short as it can be. Write a longer, more detailed version only when the user asks for one.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly