# Deliver Prd

Creates a comprehensive Product Requirements Document that aligns stakeholders on what...

- Repository: https://github.com/product-on-purpose/pm-skills (780 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add product-on-purpose/pm-skills --skill deliver-prd -g -a claude-code -y`
Codex: `npx skills add product-on-purpose/pm-skills --skill deliver-prd -g -a codex -y`
Cursor: `npx skills add product-on-purpose/pm-skills --skill deliver-prd -g -a cursor -y`
Gemini CLI: `npx skills add product-on-purpose/pm-skills --skill deliver-prd -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add product-on-purpose/pm-skills`

## Description

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
# Product Requirements Document (PRD)

A Product Requirements Document is the primary specification artifact that communicates what to build and why. It bridges the gap between problem understanding and engineering implementation by providing clear requirements, success criteria, and scope boundaries. A good PRD enables engineering to build the right thing while maintaining flexibility on implementation details.

## When to Use

- After problem and solution alignment, before engineering work begins
- When specifying features, epics, or product initiatives for handoff
- When multiple teams need to coordinate on a shared deliverable
- When stakeholders need to approve scope before investment
- As reference documentation during development and QA

## When NOT to Use

- The problem is still unframed or contested -> use `define-problem-statement` first; a PRD assumes an agreed problem
- You need a one-page pitch to align stakeholders on an approach -> use `develop-solution-brief`; the PRD comes after that alignment
- You only need the work broken into tickets for a sprint -> use `deliver-user-stories`
- You are recording a technical or architectural decision -> use `develop-adr`

## Instructions

When asked to create a PRD, follow these steps:

1. **Summarize the Problem**
   Start with a brief recap of the problem being solved. Link to the problem statement if available. Ensure readers understand *why* this work matters before diving into *what* to build.

2. **Define Goals and Success Metrics**
   Articulate what success looks like. Include specific, measurable metrics with baselines and targets. These metrics should connect directly to the problem being solved.

The rest: https://github.com/product-on-purpose/pm-skills/blob/HEAD/skills/deliver-prd/SKILL.md