PlugWiki

create-prd Skill (phuryn) for Claude: What It Does and How to Install It

Makes Claude write a lean product requirements document with market segments and a 6-part value proposition.

Installs
10.9K
on skills.sh
Stars
27.6K
on GitHub
Updated
Oct 2026
last repo commit

create-prd makes Claude write a product requirements document in eight sections: summary, contacts, background, objective, market segments, value propositions, solution and release. It is lean by default, about one to two pages or 600 to 1,000 words, and goes longer only when you ask. If the problem, target users or success metric is missing, it asks up to three short questions first.

Claude may search the web for market, competitors and regulations and cites the source next to the claim. It saves the result as PRD-[product-name].md. The skill also reviews an existing PRD and returns the gaps first, then the cuts. What it does not know goes into an assumptions and open questions section, not the body as fact.

Good for

  • Product managers who need a first PRD the team can read in minutes
  • Founders turning an idea into a spec for engineers
  • Teams reviewing an existing PRD for gaps and cuts
  • Engineers and designers who want the problem and segments stated first

Install create-prd

Claude Code

  1. 1

    Copy this prompt.

    Install the create-prd skill in Claude Code. Run this command:
    
    claude plugin marketplace add phuryn/pm-skills
    claude plugin install pm-execution@pm-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin routes install the whole pm-execution plugin: 16 skills and 11 commands (counted from the plugin folder in the repo tree, which has no hooks, agents or MCP config files). The Claude app route adds every plugin in the marketplace; the README says 9. The skills-only routes install just this skill, with no commands.

From the project README. Source.

What's in the skill

When it loads

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. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Sections in SKILL.md

  1. Purpose
  2. Lean by default
  3. Instructions
  4. Reviewing an existing PRD
  5. Notes
  6. Further Reading

Key facts

License
MIT
Installs on skills.sh
10,935 (Nov 2, 2026)
Last repo commit
Oct 29, 2026

What it includes

  • About 1 to 2 pages (600 to 1,000 words); longer only on request

    Sections with little to say get a line or two. Contacts are left out if unknown. No padding and no TBD.

    Read · Lean by default

  • Up to three short questions if problem, users or success metric is missing

    Claude replies with questions and no PRD until you answer, unless you tell it to go ahead. Then gaps are marked as assumptions.

    Read · Ask first

  • Web search for market, competitors, regulations, what changed

    Cites the source next to the claim. A finding goes in the document only if it changes a decision.

    Network · Research

  • Summary, contacts, background, objective, segments, value propositions, solution, release

    Objective has one to three measurable key results. Solution has UX/prototypes, key features, technology and assumptions. Release uses relative timeframes.

    Write · Eight sections

  • Who, why, what before, how, what after, alternatives

    One per segment, ending in a one or two sentence statement. SKILL.md credits Paweł Huryn and Aatir Abdul Rauf for the template.

    Write · 6-part value proposition

  • Writes PRD-[product-name].md

    SKILL.md names the file format and name.

    Write · Save the PRD

  • One line in the reply listing what was skipped on purpose

    For example competitive analysis, detailed UX flows or a rollout plan, so you can ask for more.

    Read · Say what was left out

  • Checks for blockers, segments, value propositions and cuts

    Returns the gaps first, then what could be cut.

    Read · Review an existing PRD

From the official docs

Permissions

Low risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Web research can include your product details

    SKILL.md tells Claude to search the web for market, competitors and regulations. Keep confidential details out of the prompt, or tell Claude not to search. github.com

  • The plugin route adds 11 commands

    The pm-execution plugin holds 16 skills and 11 commands, with no hooks, agents or MCP config files in its folder. The Claude app Cowork route adds every plugin in the marketplace. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only mode. Review the file before using it.
Scopes
  • Claude writes a markdown file named PRD-[product-name].md

  • SKILL.md tells Claude to search the web and read sources you point to

Questions

What does the create-prd skill do?

It makes Claude write a lean, decision-ready PRD from the product or feature you describe. It always includes market segments and a 6-part value proposition for each segment.

How do I install create-prd?

Use the install box at the top of this page. It offers the pm-execution plugin route for Claude Code, Codex and the Claude app, plus skills-only options that skip the plugin's commands.

Does it ask questions before writing?

Yes, if the problem, the target users or the success measure is missing. It asks up to three short questions in one message and writes no PRD in that reply. If you tell it to go ahead, it writes the PRD and marks the gaps as assumptions.

How long is the PRD?

About one to two pages, roughly 600 to 1,000 words. A PRD with two or three segments can run longer. A fuller version comes only when you ask for it.

What is the difference between the create-prd skill and the /write-prd command?

/write-prd is a command in the same pm-execution plugin. Its file says it applies the create-prd skill and its 8-section template. The command also asks the three gap questions. The skill is what you get from a skills-only install, without the commands.

Does it search the web?

It can. SKILL.md tells Claude to research freely when it helps and to read sources you point to. Claude cites the source next to each claim it uses.

Does it work in Codex or Cursor?

The README documents Codex CLI as a plugin route and says the slash commands do not run there. For Cursor, Gemini CLI, OpenCode and Kiro it says to copy the skill folders in, and skills work without the commands.

Is it safe?

The skill is one SKILL.md and bundles no scripts. When you use it, Claude writes a markdown file named PRD-[product-name].md and may search the web for your topic, so avoid putting confidential details in a prompt you would not search for. Review the PRD before sharing it.

Information

updated Nov 2, 2026

Folder
pm-execution/skills/create-prd

phuryn/pm-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. create-prd SKILL.md · github.com
  2. phuryn/pm-skills README · github.com
  3. pm-execution plugin.json · github.com
  4. write-prd.md command · github.com

Updated Nov 2, 2026.