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.
59
67%
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 template structure) and when to use it (with explicit trigger scenarios). It uses third person voice, includes natural trigger terms users would say, and is concise without unnecessary padding. The description is well-structured and would allow Claude to confidently select this skill from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and outputs: creating a PRD using an 8-section template, and names specific sections (problem, objectives, segments, value propositions, solution, release planning). | 3 / 3 |
Completeness | Clearly answers both 'what' (create a PRD using a comprehensive 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 'release planning' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%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 reasonable PRD template structure but suffers from verbosity, explaining concepts Claude already understands and lacking concrete output examples. The workflow is sequential but missing validation steps for a document-creation task where completeness and cross-section consistency matter. The skill would benefit significantly from trimming unnecessary context, adding at least one concrete example of a completed section, and introducing a validation checklist.
Suggestions
Remove the 'Purpose' persona framing and 'Context' section entirely—Claude knows what a PRD is and doesn't need to be told it's an experienced PM. Start directly with the template instructions.
Add a concrete example of at least one completed section (e.g., a sample Summary or sample Key Results in SMART OKR format) so Claude understands the expected output quality and style.
Add a validation checklist step after drafting (e.g., 'Verify: all 8 sections present, assumptions explicitly flagged, Key Results are measurable, Value Propositions link back to Objectives').
Extract the detailed 8-section template into a separate reference file (e.g., PRD-TEMPLATE.md) and keep SKILL.md as a concise overview with a reference link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is verbose with unnecessary framing ('You are an experienced product manager'), explains obvious concepts Claude already knows (what a PRD is, why it matters), includes a 'Context' section that adds no actionable value, and the 'Think Step by Step' section tells Claude to do what it naturally does. The 'Further Reading' links are not actionable by Claude without web access being guaranteed. | 1 / 3 |
Actionability | The 8-section template provides a concrete structure with specific prompts for each section, which is useful guidance. However, there are no concrete examples of what good output looks like for any section—no sample Summary, no example Key Results in SMART OKR format, no example Value Proposition. The guidance remains at the level of questions to answer rather than demonstrating expected output quality. | 2 / 3 |
Workflow Clarity | The steps are listed in a reasonable sequence (gather info → analyze → apply template → write → save), but there are no validation checkpoints. For a document this substantial, there should be a review/validation step (e.g., check all 8 sections are complete, verify assumptions are flagged, confirm alignment between objectives and value propositions). The save step mentions a naming convention which is helpful. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no bundle files to reference. The 8-section template details could be split into a separate reference file, keeping the SKILL.md as a concise overview. The external 'Further Reading' links are not part of the bundle and may not be accessible. For a skill with this much structured content, better organization across files would improve usability. | 2 / 3 |
Total | 7 / 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
d384f0c
- 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.