write-prd

Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.

Quality

86%

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

Quality

Content

78%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 strong instruction-only skill body: a clearly sequenced workflow with two validation checkpoints, concrete templates and naming conventions, and exemplary progressive disclosure with a single real, well-signaled reference. Minor gaps are a slightly redundant checklist/sections overlap and the absence of an explicit fix-and-retry loop after the verification checks.

Suggestions

Add a short 'if verification fails, fix the PRD and re-check' instruction after the step-7 verification and Quality Bar so the validate-fix-retry loop is explicit, lifting workflow clarity to the top anchor.

Consolidate the required-sections list and the Quality Bar checklist, which partially restate each other and the workflow steps, to trim redundant tokens.

Make 'Scale detail with risk' and 'verify with reliable sources' more concrete (e.g., name the risky categories to expand and what counts as a reliable source) to close the remaining actionability gaps.

Dimension	Reasoning	Score
Conciseness	The body is prescriptive rather than explanatory — it tells Claude what to produce (product-bet formula, required sections, file-naming pattern) without teaching PRD concepts Claude already knows. It falls short of 'every token earns its place' because the required-sections list and the Quality Bar checklist partially restate workflow steps (e.g., 'Is there at least one useful diagram?' repeats step 4's requirement).	4 / 5
Actionability	Concrete, executable guidance dominates: the product-bet template ('For [user], in [scenario], solve [problem], by [solution], measured by [metric]'), naming conventions ('markdown/<topic>-prd-<YYYYMMDD>.md'), an SVG link example, and a per-capability requirements coverage list. A few directives remain abstract ('Scale detail with risk', 'verify with reliable sources'), keeping it just below fully executable.	4 / 5
Workflow Clarity	The 7-step workflow is clearly sequenced and includes a post-write verification step ('After writing, verify the Markdown file exists and includes a diagram, goals/non-goals, requirements, acceptance criteria, metrics, launch plan, and open questions') plus a pre-finish Quality Bar checklist. It misses the top anchor's explicit feedback loop ('if errors: fix and re-validate') — no instruction on what to do when a check fails.	4 / 5
Progressive Disclosure	The SKILL.md body is a well-organized overview and the bulky template material is correctly split into one one-level-deep reference, signaled twice ('Read references/prd-template.md when drafting' and a Reference section with a one-line description of its contents); the referenced file exists in the bundle. This matches the top anchor: clear overview, well-signaled single-level reference, easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

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

An exemplary description: it states a concrete action with input sources and output location, provides an explicit 'Use when...' clause with comprehensive bilingual trigger synonyms, and occupies a distinct niche with minimal conflict risk. The only minor gap is that it describes one main action rather than enumerating several distinct capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete specifics — input sources ('product idea, feature concept, customer request, business problem, or rough product opportunity') and output form and location ('diagram-rich Markdown PRD under the current project's markdown/ directory'). It centers on a single action (write a PRD) rather than multiple distinct actions, so it falls just below the 'lists multiple specific concrete actions; comprehensive coverage' anchor.	4 / 5
Completeness	It explicitly answers both what ('Write a practical Product Requirements Document (PRD) from... Output a diagram-rich Markdown PRD under the current project's markdown/ directory') and when ('Use when the user asks to write, draft, create, generate, or save a PRD... from an idea') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Trigger terms are comprehensive with natural synonyms in two languages: 'PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD', plus natural verbs ('write, draft, create, generate, or save'). This matches the 'comprehensive coverage of natural terms including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	PRD/product-spec authoring is a clear niche with distinct triggers ('PRD', 'product requirements document', '产品需求文档'); overlap risk with generic documentation skills is minimal. It is not below this level because the named artifacts and bilingual keywords are unambiguous.	5 / 5
	Total	19 / 20 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: digoal/blog
Path: skills/write-prd/SKILL.md
Commit: 69fb793

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