prd-development

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/prd-development/SKILL.md

Quality

Content

45%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 content lays out a clear, well-sequenced 8-phase PRD workflow with actionable formats and skill references, but it is notably verbose and over-explains PM concepts Claude already knows. Its progressive-disclosure structure is broken because the essential referenced files (template.md, examples/sample.md) are missing from the bundle.

Suggestions

Remove or drastically trim the 'What is a PRD', 'Why This Works', 'Anti-Patterns', and 'Common Pitfalls' sections and the verbatim repeat of the intent in 'Purpose' — Claude already knows what a PRD is.

Provide the missing `template.md` (and `examples/sample.md`) as bundle files, or inline the essential per-section coaching/gap-tagging/self-assessment directly so the workflow is executable as shipped.

Move the long inline full-PRD markdown examples (problem statement, solution overview, user stories) into `examples/sample.md` and reference them one level deep to tighten SKILL.md into an overview.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the 'Purpose' section repeats the frontmatter intent verbatim, and 'What is a PRD', 'Why This Works', 'Anti-Patterns', and five 'Common Pitfalls' blocks explain PM concepts Claude already knows, alongside very long inline full-PRD examples — several padded sections, beyond 'minor' over-explanation.	2 / 5
Actionability	Concrete guidance is present (per-phase skill references like `skills/problem-statement/SKILL.md`, fill-in formats, and section examples), but it is incomplete because the central executable artifact `template.md` — described as holding the per-section coaching, gap tagging, and self-assessment — is referenced yet absent from the bundle.	3 / 5
Workflow Clarity	Eight phases are clearly sequenced with per-phase Goal/Activities/Outputs and a day-by-day end-to-end summary, plus described cross-section 'Before moving on' checks and a post-Section-10 self-assessment; minor validation gaps remain because the checkpoints live in the missing template rather than inline.	4 / 5
Progressive Disclosure	The core referenced artifact (`template.md`) and `examples/sample.md` are signaled but do not exist in the bundle, so the disclosure structure is non-functional, and large full-PRD example blocks that belong in a separate examples file are inlined in SKILL.md.	2 / 5
	Total	11 / 20 Passed

Description

78%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 well-formed: it states a concrete capability and pairs it with an explicit 'Use when' trigger, answering both what and when. It is slightly limited on specificity (one primary action) and has minor overlap risk with sibling PM-artifact skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('structured PRD') and one concrete action ('Build a structured PRD that connects problem, users, solution, and success criteria'), but does not enumerate multiple distinct actions — closer to 'names domain and 1-2 concrete actions' than to 'lists several specific actions.'	3 / 5
Completeness	Explicitly answers both what ('Build a structured PRD that connects problem, users, solution, and success criteria') and when ('Use when turning discovery notes into an engineering-ready document for a major initiative') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural PM terms ('PRD', 'discovery notes', 'engineering-ready document', 'major initiative') that users would actually say, with only minor synonyms missing (e.g., 'product requirements document', 'spec').	4 / 5
Distinctiveness Conflict Risk	PRD creation is a clear niche with distinct triggers, but there is minor overlap risk with adjacent PM-artifact skills (specs, RFCs) — mostly distinct rather than minimal conflict risk.	4 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (674 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/prd-development/SKILL.md
Commit: a03af68

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