create-prd-feature

Create a feature-specific PRD (FRD) for individual features

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/create-prd-feature/SKILL.md

Quality

Content

77%

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

This skill provides excellent actionability with concrete prompts, examples, and a clear sequential workflow for creating feature-level PRDs. The main weakness is verbosity - the extensive inline prompts and examples make it longer than necessary, and the content could benefit from better progressive disclosure by moving detailed section prompts to a reference file.

Suggestions

Move the detailed section prompts (sections 1-13) to a separate reference file like `frd-prompts.md` and keep only the high-level flow in SKILL.md

Consolidate redundant guidance - 'Tips for Claude Code' and 'Task Generation Guidelines' overlap with inline instructions in the sections

Dimension	Reasoning	Score
Conciseness	The content is moderately efficient but includes some redundancy. The 13 sections with detailed prompts are comprehensive but could be tightened - some questions are repetitive across sections, and the extensive example formats add bulk that Claude could infer.	2 / 3
Actionability	Provides highly concrete guidance with specific section-by-section prompts, example formats (Given/When/Then, API specs, task breakdown format), and clear execution instructions. The interactive session flow is copy-paste ready for implementation.	3 / 3
Workflow Clarity	Clear 13-step sequential workflow with numbered sections, explicit progress indicators ([Section X of 12]), and a final review checkpoint. The flow from context gathering through task breakdown to business deliverables is logical and well-structured.	3 / 3
Progressive Disclosure	References an external template file (frd-template.md) appropriately, but the skill itself is a monolithic document. The detailed section prompts could be split into a separate reference file, with SKILL.md providing just the overview and flow structure.	2 / 3
	Total	10 / 12 Passed

Description

32%

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 identifies a specific document type (feature-specific PRD/FRD) but is too brief to be effective for skill selection. It lacks explicit trigger conditions, concrete actions beyond 'create', and natural keyword variations that users might employ when requesting this type of work.

Suggestions

Add a 'Use when...' clause with trigger terms like 'feature requirements', 'product spec', 'FRD', 'feature documentation', 'requirements document'

List specific concrete actions such as 'define acceptance criteria', 'document user stories', 'outline technical requirements', 'specify feature scope'

Include common keyword variations users might say: 'feature spec', 'product requirements', 'requirements doc', 'feature definition'

Dimension	Reasoning	Score
Specificity	Names the domain (PRD/FRD creation) and specifies it's for 'individual features', but doesn't list concrete actions like 'define requirements', 'outline acceptance criteria', or 'document user stories'.	2 / 3
Completeness	Only answers 'what' (create FRD for features) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'PRD' and 'FRD' which are relevant terms, but misses common variations users might say like 'product requirements', 'feature spec', 'requirements document', or 'feature documentation'.	2 / 3
Distinctiveness Conflict Risk	The PRD/FRD focus provides some distinction, but could overlap with general documentation skills or broader product management skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.