SkillAgentSearch skills...

create-prd

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request

Install / Use

npx skills add phuryn/pm-skills --skill create-prd

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of create-prd

create-prd scores 85/100 on our quality scale, 766th of 1,155 Content & Media skills we index.

Its SKILL.md is 3.5 KB long, split into 6 sections and no code examples: a solid amount of guidance for an agent.

With 26,568 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so create-prd is actively maintained.
  • Our last check on 2026-10-12 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

create-prd compared with similar skills

All 4 of these similar skills score higher than create-prd; compare them before choosing.

SkillScoreStarsUpdatedFormat
create-prd (this skill)by phuryn8526.6k2mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install create-prd?
Run npx skills add phuryn/pm-skills --skill create-prd. The install tabs above show the steps for each supported agent.
Which AI agents does create-prd work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is create-prd safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is create-prd still maintained?
The repository was last updated about 2 months ago, so create-prd is actively maintained.

name: create-prd description: "Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD."

Create a Product Requirements Document

Purpose

You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.

Context

A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.

Instructions

  1. Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.

  2. Think Step by Step: Before writing, analyze:

    • What problem are we solving?
    • Who are we solving it for?
    • How will we measure success?
    • What are our constraints and assumptions?
  3. Apply the PRD Template: Create a document with these 8 sections:

    1. Summary (2-3 sentences)

    • What is this document about?

    2. Contacts

    • Name, role, and comment for key stakeholders

    3. Background

    • Context: What is this initiative about?
    • Why now? Has something changed?
    • Is this something that just recently became possible?

    4. Objective

    • What's the objective? Why does it matter?
    • How will it benefit the company and customers?
    • How does it align with vision and strategy?
    • Key Results: How will you measure success? (Use SMART OKR format)

    5. Market Segment(s)

    • For whom are we building this?
    • What constraints exist?
    • Note: Markets are defined by people's problems/jobs, not demographics

    6. Value Proposition(s)

    • What customer jobs/needs are we addressing?
    • What will customers gain?
    • Which pains will they avoid?
    • Which problems do we solve better than competitors?
    • Consider the Value Curve framework

    7. Solution

    • 7.1 UX/Prototypes (wireframes, user flows)
    • 7.2 Key Features (detailed feature descriptions)
    • 7.3 Technology (optional, only if relevant)
    • 7.4 Assumptions (what we believe but haven't proven)

    8. Release

    • How long could it take?
    • What goes in the first version vs. future versions?
    • Avoid exact dates; use relative timeframes
  4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

  5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.

  6. Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: PRD-[product-name].md

Notes

  • Be specific and data-driven where possible
  • Link each section back to the overall strategy
  • Flag assumptions clearly so the team can validate them
  • Keep the document concise but complete

Further Reading

Related Skills

View on GitHub
GitHub Stars26.6k
CategoryContent
Updated2mo ago
Forks2.8k

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
create-prd — Universal Skill: Install & Safety Check | SkillAgent