Skip to content
SkillModel-led1,607 tokens in use

create-prd

Write a lean, decision-ready PRD in eight sections with market segments and a 6-part JTBD value proposition, or review an existing PRD.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/create-prd
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing create-prd costs

85tokens idle
1,607tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples3/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

create-prd has an agent write a Product Requirements Document that a team can read in a few minutes: summary, contacts, background, objective, market segments, value propositions, solution and release. It starts from what you provide, asks up to three short questions if the problem, users or success metric are missing, and can research the web. It can also review an existing PRD for gaps and cuts.

What You Get

  • A PRD saved as a markdown file named for the product
  • Eight sections with an OKR-style objective and one to three key results
  • A 6-part JTBD value proposition per segment: who, why, what before, how, what after, alternatives
  • A solution section with key features, assumptions and open questions
  • A release section covering the first version, later work and what is out of scope
  • A short note in the reply on what was skipped on purpose

Common Use Cases

  • Writing a first PRD for a new feature
  • Reviewing an existing PRD for missing decisions
  • Preparing a short spec for engineers and designers

What Makes It Unique

It is lean by default and built around a value proposition for each segment, so the solution delivers the how and the key results measure the what after. It asks for missing problem, user and metric information before writing.

Under The Hood

The skill is one SKILL.md of instructions with no bundled scripts. The agent reads files you provide, may search the web for market and competitor facts and cites them next to the claim, then saves the PRD as a markdown file. It points to the value-proposition skill of a sibling plugin when that is installed.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers