vibe-prd

Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/vibe-prd/SKILL.md

Quality

Content

62%

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

A clearly sequenced, well-organized PRD-generation workflow with a solid validation echo, but it leans on an external (possibly missing) file for all its actionable content and carries some redundant coaching that could be trimmed.

Suggestions

Bundle the question bank and PRD template as a reference file under references/ (or inline the essential questions) so the skill is self-contained instead of depending on a part2-prd-mvp.md file that may not exist.

Trim the "Self-Verification" checklist and consolidate "Session Continuity"/"Naming Policy" to reduce token overhead that does not directly drive the workflow.

Add at least one short inline example of a completed verification-echo block or a minimal PRD excerpt so the guidance is copy-paste ready without the external file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with numbered steps and blockquoted prompts and no concept-explaining padding, but the "Self-Verification" checklist and "Session Continuity"/"Naming Policy" sections add some redundancy that could be tightened.	2 / 3
Actionability	Gives concrete file paths, level-based routing (Path A/B/C), and a literal verification-echo template, but the actual question bank and PRD template are fully externalized to part2-prd-mvp.md (not bundled here), leaving key details out of the skill itself.	2 / 3
Workflow Clarity	A clear five-step sequence with an explicit validation checkpoint (the Verification Echo) and a feedback loop ("Do NOT generate the PRD until all essential answers are collected" / "Is this accurate?"), matching the score-3 anchor.	3 / 3
Progressive Disclosure	Well-sectioned body with a clearly signaled one-level reference to part2-prd-mvp.md, but no skill bundle files are shipped and the key reference is an external project file that may be absent, making the split fragile rather than a proper bundled disclosure.	2 / 3
	Total	9 / 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-formed description with an explicit "Use when" trigger clause and natural user phrasings. Its only weakness is that it names a single core action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the concrete domain and action ("Create a Product Requirements Document (PRD) for your MVP") but lists only one core action rather than multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	Explicitly answers what ("Create a ... PRD for your MVP") and when via an explicit "Use when the user wants to define product requirements, create a PRD, or says..." trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural user phrasings ("define product requirements", "create a PRD", "help me write requirements", "define my product") that a user would realistically say, matching the good coverage anchor.	3 / 3
Distinctiveness Conflict Risk	PRD/MVP creation is a clear niche with distinct triggers ("create PRD", "define my product") unlikely to conflict with other skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: KhazP/vibe-coding-prompt-template
Path: .claude/skills/vibe-prd/SKILL.md
Commit: 06d0796

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