Agent skill · Workflow & Productivity

deliver-prd

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.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill deliver-prd --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 4 KB
Bundled scripts: none
Version: 2.1.0
Declared author: product-on-purpose
Path: skills/deliver-prd/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- 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

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Instructions
  4. Output Format
  5. Quality Checklist
  6. Examples
Ships with 4 files
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the deliver-prd skill do?

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.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill deliver-prd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going