prp-prd

Interactive PRD generator - problem-first, hypothesis-driven product spec. Use when the user wants to create a PRD, write a product or feature spec, scope a new product, or invokes the prp-prd skill.

Quality

88%

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

Quality

Content

77%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced interactive workflow with concrete templates and validation gates, but it is long and monolithic. Conciseness and progressive disclosure are the weakest dimensions due to repeated boilerplate and an inline template that would benefit from extraction.

Suggestions

Extract the ~150-line PRD template (and the Phase 8 output template) into a references/ file (e.g. references/prd-template.md) and link to it, turning SKILL.md into a lean overview with one-level-deep, well-signaled references.

Remove the repeated "Do the X analysis below inline (kild lane: no subagents)" disclaimers by stating the no-subagent convention once, cutting several redundant blocks across Phases 3 and 5.

Trim or relocate the top 'kild lane' boilerplate so it does not compete with the skill's own purpose and process overview for the reader's first tokens.

Dimension	Reasoning	Score
Conciseness	The core phases and templates are efficient, but the ~480-line body is padded with repeated "(kild lane: no subagents)" disclaimers, a top boilerplate block, and a 150-line inline PRD template that could be tightened or extracted. Not a 3 because not every token earns its place; not a 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides executable bash for PRP_DIR resolution, a concrete output path, a copy-paste PRD template, and structured FIND/LOCATE/TRACE research prompts. Fully executable and copy-paste ready.	3 / 3
Workflow Clarity	Eight phases are clearly sequenced with explicit GATE checkpoints ("Wait for user response before proceeding") plus an ASCII flow diagram. Not capped at 2 because this is an interactive generation workflow, not a destructive/batch operation.	3 / 3
Progressive Disclosure	Sections are well-organized, but the body is monolithic with no external reference files; the large PRD template and output template are inline content that could be split out. Not a 3 because there are no one-level-deep, well-signaled references; not a 1 because organization is clear rather than a wall of text.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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: third-person voice, concrete capabilities, explicit 'Use when' triggers, and a distinct niche. It cleanly satisfies both the 'what' and 'when' requirements.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ("create a PRD, write a product or feature spec, scope a new product") rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers what ("Interactive PRD generator - problem-first, hypothesis-driven product spec") and when ("Use when the user wants to create a PRD..."), with an explicit trigger clause. Not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	Uses natural phrasing a user would actually say ("create a PRD", "product or feature spec", "scope a new product") with good coverage; not jargon or overly generic.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear PRD/product-spec niche with distinct triggers and even names the prp-prd skill, making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Wirasm/prp
Path: profiles/kild/skills/prp-prd/SKILL.md
Commit: 1142738

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