CtrlK
BlogDocsLog inGet started
Tessl Logo

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 /prp-prd.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A highly actionable, well-sequenced interactive workflow with explicit gating checkpoints and copy-paste-ready tooling. Its main weakness is progressive disclosure: everything is inlined into one long SKILL.md with no reference or script bundle files.

Suggestions

Move the ~150-line PRD template into a references/ file (e.g. references/prd-template.md) and reference it from Phase 7 to reduce SKILL.md length and improve progressive disclosure.

Extract the bash PRP store resolver into a scripts/ file and invoke it from the skill, rather than inlining the full script block.

Remove or condense the closing 'Question Flow Summary' ASCII diagram since it restates the phase sequence already covered by the phase headings and Process Overview.

DimensionReasoningScore

Conciseness

The body is dense and purposeful with no conceptual over-explanation (it never explains what a PRD is), though the closing ASCII 'Question Flow Summary' repeats the phase sequence already detailed above and could be trimmed.

4 / 5

Actionability

Fully executable guidance: exact questions to ask, concrete subagent_type invocations, a copy-paste-ready bash store resolver, a complete PRD template, and a precise output path cover the common cases.

5 / 5

Workflow Clarity

Eight phases are clearly sequenced with explicit 'GATE: Wait for user response' checkpoints between each, grounding phases that validate assumptions, and a closing Success Criteria checklist - matching the explicit-validation/feedback-loop anchor.

5 / 5

Progressive Disclosure

The file is well-sectioned but entirely monolithic at ~480 lines with no bundle files: the large PRD template and bash resolver are inlined rather than split into reference/script files, so content that could live one level deeper is inline.

3 / 5

Total

17

/

20

Passed

Description

83%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.

A strong, well-formed description that clearly states what the skill does and when to invoke it using natural trigger terms and a slash command. It is concise, third-person, and specific, with only minor room for broader synonym coverage.

DimensionReasoningScore

Specificity

Names the domain (PRD/product spec) and lists several concrete actions - 'create a PRD, write a product or feature spec, scope a new product' - with only minor coverage gaps, falling just short of the comprehensive multi-action anchor at 5.

4 / 5

Completeness

Explicitly answers both what ('Interactive PRD generator - problem-first, hypothesis-driven product spec') and when ('Use when the user wants to create a PRD... or invokes /prp-prd') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural user phrases ('create a PRD', 'write a product or feature spec', 'scope a new product') plus the '/prp-prd' invocation, though a few common synonyms like 'requirements doc' are absent.

4 / 5

Distinctiveness Conflict Risk

The PRD/product-spec niche and the '/prp-prd' slash command give it distinct triggers with minimal conflict risk, though it could marginally overlap with general product-planning skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
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.