create-prd

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clear, well-structured instruction skill with concrete template guidance and a sensible workflow. It could be tightened by trimming the Purpose/Context padding and adding a final validation step plus a brief worked example.

Suggestions

Trim the Purpose and Context sections — remove restatements of what a PRD is and the 'proven to communicate product vision' marketing claim, since Claude already knows this.

Add a final validation step to the workflow, e.g. 'Review the draft against the 8-section template to confirm every section is present and SMART OKRs are filled in before saving.'

Include a short worked example (a few lines of one filled-in section) so the expected output style is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with bullet-prompted sections and named frameworks; the Purpose and Context paragraphs restate what a PRD is ('aligning stakeholders and guiding development', 'proven to communicate product vision') which Claude already knows — minor trimming possible.	4 / 5
Actionability	Provides concrete, specific guidance: the 8-section template, SMART OKR format, Value Curve framework, relative-timeframe rule, and the output filename pattern 'PRD-[product-name].md'; not a 5 because it lacks a worked example of actual PRD output.	4 / 5
Workflow Clarity	Six clearly numbered steps with a pre-write 'Think Step by Step' checkpoint form a coherent sequence; not a 5 because there is no final review/validation checkpoint confirming all 8 sections are present before saving.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear headers (Purpose, Context, Instructions, Notes, Further Reading) and the template content appropriately inline; no bundle files exist, and external 'Further Reading' links are clearly signaled, but the file runs slightly long for a fully lean overview.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit what-and-when structure, and concrete trigger phrases. Minor room to broaden trigger synonyms and add a second concrete action verb.

Dimension	Reasoning	Score
Specificity	Names the domain and lists concrete coverage ('problem, objectives, segments, value propositions, solution, and release planning'), which is several specific components; not a 5 because the only action is 'Create' a PRD rather than multiple distinct operations.	4 / 5
Completeness	Explicitly answers what ('Create a Product Requirements Document using a comprehensive 8-section template...') and when ('Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'writing a PRD', 'documenting product requirements', 'preparing a feature spec', and 'reviewing an existing PRD' give good coverage with synonyms; a few natural variants (e.g. 'requirements doc', 'product spec') are missing.	4 / 5
Distinctiveness Conflict Risk	PRD creation is a clear niche with distinct triggers (PRD, feature spec, product requirements) and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-execution/skills/create-prd/SKILL.md
Commit: 8607e3b

Reviewed: 18 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.