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

96%

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

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

The skill body is well-structured, actionable, and concise, with a clear sequenced workflow that includes explicit validation and a final quality checklist. Its only weakness is minor rhetorical padding that slightly undercuts token efficiency.

Suggestions

Tighten the framing lines such as 'A good PRD is not a feature list; it is a clear product bet' and the Quality Bar rhetorical questions into terse imperative checks to save tokens.

The 'Output Requirements' and 'Quality Bar' sections overlap on required sections and verification; consolidate to reduce redundancy.

Consider moving the full list of required PRD sections into the referenced template and keeping only the canonical structure in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence with no padded concept explanations; a few rhetorical framing lines ('A good PRD is not a feature list; it is a clear product bet') could be trimmed, placing it just below level 5.	4 / 5
Actionability	Provides concrete executable guidance: explicit file-name patterns ('markdown/<topic>-prd-<YYYYMMDD>.md'), a fill-in product-bet template ('For [user], in [scenario], solve [problem], by [solution], measured by [metric]'), and a real referenced template file, fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	A 7-step sequence with step 7 as an explicit validation checkpoint ('verify the Markdown file exists and includes a diagram, goals/non-goals, requirements...') plus a closing Quality Bar checklist, matching the level-5 anchor with clear validation and feedback structure.	5 / 5
Progressive Disclosure	The body is a well-organized overview with a single clearly-signaled one-level-deep reference to the real file 'references/prd-template.md', keeping detail appropriately split and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is exemplary: it states concrete capabilities, provides exhaustive bilingual trigger terms, and explicitly covers both what the skill does and when to invoke it. It is clearly distinguishable from other writing skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Write', 'draft', 'create', 'generate', or 'save a PRD', 'Output a diagram-rich Markdown PRD') with comprehensive coverage of the PRD-writing capability, matching the level-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' ('Write a practical Product Requirements Document') and 'when' ('Use when the user asks to write, draft, create...') with concrete trigger phrases, matching the level-5 anchor.	5 / 5
Trigger Term Quality	Comprehensive bilingual trigger coverage ('write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明'), covering natural synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The PRD niche has clear distinct triggers and a specific output location; bilingual terms and the PRD-specific vocabulary give it minimal conflict risk with other skills.	5 / 5
	Total	20 / 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: 3b9c83d

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