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.
64
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-execution/skills/create-prd/SKILL.mdQuality
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. The only minor improvement could be mentioning additional trigger terms like 'product spec' or 'requirements doc'.
| 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 four 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 skill provides a solid PRD template structure with useful guiding questions for each section, but it suffers from unnecessary preamble, lack of concrete output examples, and missing validation/review steps. The content would benefit from trimming the introductory fluff, adding a brief example of at least one completed section, and including a review checklist to verify PRD completeness.
Suggestions
Add a concrete example of at least one completed PRD section (e.g., a sample Summary or Objective) to make the template more actionable and show expected output quality.
Remove the 'Purpose' and 'Context' sections or compress them significantly—Claude doesn't need to be told it's an experienced PM or what a PRD is.
Add a validation/review step after drafting (e.g., 'Review: verify each section answers its guiding questions, check that Key Results are SMART, confirm assumptions are flagged') to improve workflow clarity.
Consider replacing 'Think Step by Step' with inline annotations in the template itself, reducing redundancy between the analysis questions and the template's guiding questions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('You are an experienced product manager...'), explains what a PRD is (Claude already knows), and the Context section adds little value. The template itself is reasonably efficient but could be tighter. | 2 / 3 |
Actionability | The 8-section template provides a clear structure with guiding questions, which is useful. However, it lacks a concrete example of a completed section or even a partial PRD output, making it more of a checklist than fully actionable guidance. The instruction to 'save as PRD-[product-name].md' is a nice concrete detail. | 2 / 3 |
Workflow Clarity | Steps are listed (gather info, think, apply template, write, save) but there are no validation checkpoints—no step to review the PRD against requirements, verify completeness of sections, or get feedback. For a document-generation task, a review/validation step would improve quality assurance. | 2 / 3 |
Progressive Disclosure | All content is inline in a single file, which is borderline acceptable for this length. The 'Further Reading' links at the bottom are a nice touch but are external URLs rather than companion files. The detailed template subsections (especially Section 7 with its sub-parts) could benefit from being referenced separately if they were more detailed. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%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
020ee82
- Reviewed
Table of Contents
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.