CtrlK
BlogDocsLog inGet started
Tessl Logo

write-prd

Produce a comprehensive Product Requirements Document (PRD). Use when the user asks to write a PRD or formalize a feature's scope, goals, and success metrics.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/flowai-engineering/skills/write-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable PRD guide with a clear workflow and template. It is slightly verbose in places and fully self-contained with no external references, which is reasonable for this skill.

Suggestions

Trim the meta-commentary ('This rule is designed to apply Prompt Engineering principles...') and condense the Core Principles section to reduce token overhead.

Add one fully worked example PRD (even briefly) so the template's placeholders are demonstrably executable end-to-end.

Consider moving the full template and Bad/Good examples into a reference file, leaving SKILL.md as a concise overview with a clearly signaled link.

DimensionReasoningScore

Conciseness

Mostly efficient with a usable template and examples, but includes unnecessary padding such as 'This rule is designed to apply Prompt Engineering principles—clarity, constraints, and structure—to documentation' and an abstract Core Principles section that could be tightened.

3 / 5

Actionability

Provides a copy-paste-ready PRD template with concrete section structure and concrete Bad/Good examples; minor gaps in that no fully worked end-to-end PRD example is shown.

4 / 5

Workflow Clarity

Clear 5-step sequence (Analyze, Ask, Draft, Review, Persist) with a Review checkpoint and a CRITICAL persist-to-file instruction; no error-recovery feedback loop, but acceptable for a non-destructive document-writing task.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references; the template is appropriately the core inline content. Slightly below 5 because the full template/examples could optionally live in a reference file for a leaner SKILL.md.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong: it is third-person, clearly states what the skill does, and provides explicit 'Use when' trigger guidance with concrete natural phrases. Minor improvement possible by adding synonyms like 'spec' or 'requirements doc'.

DimensionReasoningScore

Specificity

Names the PRD domain and lists several concrete facets—'write a PRD', 'formalize a feature's scope, goals, and success metrics'—matching the anchor that lists several specific actions with minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Produce a comprehensive Product Requirements Document (PRD)') and when ('Use when the user asks to write a PRD or formalize...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('write a PRD', 'formalize a feature's scope, goals, and success metrics') with good coverage, but misses common synonyms like 'requirements doc', 'spec', or 'product spec'.

4 / 5

Distinctiveness Conflict Risk

PRD authoring is a clear niche with distinct triggers; minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
korchasa/flowai-plugins
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.