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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

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

A well-structured, actionable instruction skill with a concrete template and clear sequencing. It loses points for some unnecessary explanatory framing and the absence of an explicit review/validation step in the workflow.

Suggestions

Tighten the Purpose and Context sections: drop the PRD-is-good-because explanation and role-play framing, keeping only what guides the output (the template and its constraints).

Add an explicit review/validation step to the workflow, e.g. a final pass that checks each section against the template checklist before saving the PRD.

Replace generic reminders in Notes with a concise completion checklist (e.g. "Every section links to strategy; assumptions flagged; relative timeframes only") so the quality bar is verifiable.

Dimension	Reasoning	Score
Conciseness	The body is mostly a lean, useful template, but the Purpose/Context sections add explanation Claude already knows ("A well-structured PRD clearly communicates the what, why, and how…", the role-play framing), matching the "mostly efficient but includes some unnecessary explanation" anchor.	2 / 3
Actionability	As an instruction-only skill it provides concrete, specific guidance: a precise 8-section template with per-section prompts, directives ("Use SMART OKR format", "Avoid exact dates; use relative timeframes"), and a concrete save format PRD-[product-name].md.	3 / 3
Workflow Clarity	There is a clear numbered sequence (Gather → Think → Apply template → Language → Structure → Save), but no validation or review checkpoint, matching the "steps listed but checkpoints missing or implicit" anchor rather than the level-3 anchor that requires explicit validation steps.	2 / 3
Progressive Disclosure	The skill is well-organized into clear sections, is appropriately self-contained with no need for bundle files, and its only external links (Further Reading) are clearly signaled one-level references, satisfying the well-organized/simple-skill guidance.	3 / 3
	Total	10 / 12 Passed

Description

90%

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

A strong, well-structured description with an explicit Use-when trigger clause and good natural-term coverage. Its only weakness is that it elaborates a single action via template sections rather than enumerating multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	The description centers on a single action ("Create a Product Requirements Document") and then enumerates template sections (problem, objectives, segments…) rather than listing multiple distinct concrete actions the skill performs, matching the "names domain and some actions" anchor rather than the multi-action level 3.	2 / 3
Completeness	It explicitly answers both what ("Create a Product Requirements Document using a comprehensive 8-section template…") and when via an explicit "Use when…" clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	"writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD" gives good coverage of the natural terms a user would actually say, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The PRD/feature-spec niche has distinct triggers that are unlikely to fire for unrelated skills, matching the level-3 "clear niche with distinct triggers" anchor.	3 / 3
	Total	11 / 12 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
Commit: 18468a9

Reviewed: 15 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.