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

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./pm-execution/skills/create-prd/SKILL.md

Quality

Discovery

100%

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

This is a strong skill description that clearly communicates what the skill does (creates PRDs using a specific 8-section template), names the key sections covered, and provides explicit trigger guidance with natural user terms. It uses proper third-person voice and is concise without being vague.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and structural details: 'comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.' This clearly describes what the skill produces and its structure.	3 / 3
Completeness	Clearly answers both 'what' (create a PRD using an 8-section template covering specific areas) and 'when' (explicit 'Use when' clause with multiple trigger scenarios: writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'PRD', 'product requirements', 'feature spec', 'Product Requirements Document'. These cover common variations of how users refer to this type of document.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around PRDs and product requirements documents. The specific mention of the 8-section template structure and domain-specific terms like 'PRD', 'feature spec', and 'value propositions' make it unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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

This is a moderately well-structured instruction-only skill that provides a clear PRD template with guiding questions per section. Its main weaknesses are unnecessary preamble/context that Claude doesn't need, lack of a concrete output example, and missing validation/review steps in the workflow. The template itself is the strongest element but would benefit from tighter framing and a completion checklist.

Suggestions

Remove the 'Purpose' and 'Context' sections—Claude doesn't need to be told it's a product manager or what a PRD is. Jump straight to the template and instructions.

Add a concrete example of at least one completed section (e.g., a sample Summary or Objective) so Claude has a clear quality benchmark for output.

Add a validation/review step after drafting, such as a checklist: 'Verify all 8 sections are present, assumptions are flagged, key results are SMART, and no section references undefined terms.'

Consider extracting the full 8-section template into a separate reference file (e.g., PRD-TEMPLATE.md) and keeping SKILL.md as a concise workflow overview with a link to the template.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('You are an experienced product manager...', the Context section explaining what a PRD is, 'Write for a primary school graduate'). The template sections themselves are reasonably lean, but the preamble and meta-instructions add tokens without value for Claude.	2 / 3
Actionability	The 8-section template provides a clear structure with guiding questions for each section, which is concrete for an instruction-only skill. However, it lacks a concrete example of a completed section or expected output format, and some guidance remains abstract (e.g., 'Consider the Value Curve framework' without explaining what to do with it).	2 / 3
Workflow Clarity	Steps are listed (gather info → think → apply template → write → save), but there are no validation checkpoints. For a document-generation task, there's no review step, no checklist to verify completeness, and no feedback loop for iterating with the user on gaps or assumptions.	2 / 3
Progressive Disclosure	The content is mostly inline in a single file, which is borderline acceptable for this skill's complexity. The 'Further Reading' links are external URLs rather than companion files. The 8-section template could benefit from being a separate reference file, keeping the SKILL.md as a concise overview with navigation.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Commit: 36ccefd

Reviewed: about 8 hours 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.