CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

81%

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

70%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 well-engineered interactive workflow: the phase/gate structure is exemplary and the prompts and templates are concrete enough to execute directly. The weaknesses are bulk — redundant flow diagrams, repeated scaffolds, and an inlined ~150-line PRD template with no external references — which inflate token cost and blur the overview-vs-detail split.

Suggestions

Move the full PRD template (and optionally the PRP store resolver script) into a references/ file (e.g., references/prd-template.md) and link to it from Phase 7, keeping SKILL.md as a lean overview of the phase flow.

Delete the ASCII 'Question Flow Summary' section — it restates the 'Process Overview' diagram at the top of the file — and collapse the five repeated Goal/Scope/Success-signal phase-detail scaffolds into a single pattern with 'repeat for each phase'.

Define or link the referenced subagents (web-researcher, codebase-explorer, codebase-analyst), or reframe them as generic Agent-tool prompts, since they are invoked by name but never specified anywhere in the bundle.

DimensionReasoningScore

Conciseness

The body is mostly efficient — concrete question scripts and subagent prompts rather than explanations of concepts Claude already knows — but carries real padding: the ASCII 'Question Flow Summary' duplicates the 'Process Overview' diagram near the top, the phase-details and implementation-phase templates repeat an identical Goal/Scope/Success-signal scaffold five times, and the full ~150-line PRD template is inlined. It fits 'mostly efficient but includes some unnecessary content that could be tightened' better than anchor 4.

3 / 5

Actionability

Guidance is largely executable: verbatim question sets to present, copy-paste subagent prompts, a complete bash resolver for $PRP_DIR with an exact output path, and a fill-in PRD template. Minor gaps keep it below 'fully copy-paste ready': the subagent types (web-researcher, codebase-explorer, codebase-analyst) are referenced but never defined in the bundle, and '{kebab-case-name}' derivation is left unspecified.

4 / 5

Workflow Clarity

Eight phases are explicitly sequenced, every phase ends in a GATE ('Wait for user response before proceeding'), Phase 1 includes a restatement-correction feedback loop, Phase 3/5 summaries invite adjustments before continuing, and a closing success-criteria checklist validates the output. This matches the anchor for clear sequence, explicit validation checkpoints, feedback loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so everything is inline in a ~480-line SKILL.md. Sections are clearly headed and ordered, but the large PRD template and the PRP store resolver are content that naturally belongs in a separate reference file — the 'some structure, but content that could be separate is inline' anchor rather than the well-split anchor 4.

3 / 5

Total

15

/

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 description: it states what the skill does, how it differs (problem-first, hypothesis-driven), and gives multiple explicit natural-language triggers plus the invocation name. The only gap is a few missing synonyms (e.g., 'requirements document') that would make triggering fully comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'create a PRD', 'write a product or feature spec', 'scope a new product' — with the qualifier 'problem-first, hypothesis-driven' narrowing the approach. It stops short of comprehensive coverage (no mention of the interactive/elicitation workflow or research phases), matching the 'several specific actions; minor gaps' anchor rather than the fuller anchor 5.

4 / 5

Completeness

It explicitly answers both: what ('Interactive PRD generator - problem-first, hypothesis-driven product spec') and when ('Use when the user wants to create a PRD, write a product or feature spec, scope a new product, or invokes $prp-prd') with concrete trigger phrases — a direct match for the anchor requiring both what and when with explicit triggers.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are present: 'create a PRD', 'write a product or feature spec', 'scope a new product', plus the explicit invocation '$prp-prd'. Common synonyms like 'requirements doc', 'product requirements document', or '.prd' are missing, so it sits just below the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

The PRD/spec niche is fairly distinct and the '$prp-prd' invocation trigger is unambiguous. Minor overlap risk remains with adjacent planning or technical-spec writing skills via the phrase 'write a product or feature spec', which keeps it below the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

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

Validation for skill structure

No warnings or errors.

Repository

Wirasm/prp

Path

.agents/skills/prp-prd/SKILL.md

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.