create-prd

Generate structured Product Requirements Documents in markdown from user inputs.

2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/jasonmeans/pm-skills --skill create-prd-jasonmeans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/jasonmeans/pm-skills/tree/main/.claude/skills/create-prd
Command: npx skills add https://github.com/jasonmeans/pm-skills --skill create-prd-jasonmeans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Product Requirements Documents (PRDs), reducing the time and effort required to document features, products, or initiatives.

Core Features & Use Cases

  • PRD Generation: Automatically write a complete PRD covering problem statement, goals, user stories, success metrics, and more.
  • User Input: Gather inputs for product/feature name, problem statement, goals, target users, context, and constraints.
  • Output: Provide a structured PRD in markdown format that serves as a single source of truth for the project.

Quick Start

Create a PRD for the new notification preferences feature by providing the necessary details.

Frequently Asked Questions about create-prd

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

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

To automate product requirements document generation, provide the feature name, problem statement, goals, target users, context, and constraints. The skill processes these inputs to output a structured PRD covering problem definition, user stories, and success metrics.

What is the best way to structure user stories and success metrics in a PRD?

The best way to structure user stories and success metrics in a PRD is by providing target user details and project constraints as input. The automation then defines user stories and success metrics, documenting them alongside technical considerations in a markdown format.

What inputs are required to generate a PRD for project planning?

Generating a PRD for project planning requires inputs including the product or feature name, problem statement, goals, target users, context, and constraints. These elements are necessary to automate problem definition and technical consideration documentation.

Does PRD generation work without providing technical considerations and constraints?

PRD generation requires constraints and context as inputs to document technical considerations accurately. Without providing these inputs, the skill cannot fully automate the creation of a complete product requirements document that serves as a single source of truth.

Can I use this skill to streamline product management processes for multiple initiatives?

You can use this skill to streamline product management processes for multiple initiatives by providing specific inputs for each feature. It reduces the effort required to document products by outputting a structured markdown PRD for every initiative.