CtrlK
BlogDocsLog inGet started
Tessl Logo

prd-development

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

62

Quality

75%

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 ./skills/prd-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%

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

The content is highly actionable with concrete examples and a clear phase sequence, but it is verbose with duplicated and re-taught material, lacks in-document validation checkpoints, and depends heavily on references (template.md, workshop-facilitation, examples/sample.md, many sibling skills) that do not exist in the bundle.

Suggestions

Add the referenced bundle files (template.md, examples/sample.md) or remove the references; unverifiable paths hurt progressive disclosure and actionability at runtime.

De-duplicate the body — the Purpose section restates the intent block, and the standard template is repeated inside phases — to tighten conciseness.

Insert explicit validation checkpoints between phases (e.g. 'Before moving to Phase N, confirm prior section has evidence + acceptance criteria') so workflow clarity does not rely solely on the external template.

DimensionReasoningScore

Conciseness

The body is long but largely earns its length with phase-by-phase facilitation guidance; however it repeats material (e.g. the full PRD template appears, then each phase restates example sections, and the Purpose section duplicates the intent block verbatim) and explains well-known concepts like what a PRD is and 'What is a PRD?' with the seven canonical questions. Not level-3 lean because of the duplication and concept re-teaching; above level-1 since most content is operational rather than generic padding.

2 / 3

Actionability

Each phase gives concrete fill-in formats, worked examples (problem statement with real quotes/metrics, sample user stories with acceptance criteria, metric targets with current→goal), and explicit skill references per step. Matches the level-3 'specific examples, copy-paste ready' anchor; not level-2 because guidance is concrete and complete rather than pseudocode or abstract.

3 / 3

Workflow Clarity

The 8 phases are clearly sequenced with a Day 1–4 end-to-end summary, but there are no explicit validation checkpoints between phases (the cross-section 'Before moving on' checks live in template.md, not here) and no validate→fix→retry loop for risky steps like sign-off or scope changes. Per the rubric, missing validation/checkpoint detail caps a multi-step workflow at 2; not level-1 because the sequence is unambiguous and well-structured.

2 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are empty), yet the body references external paths that cannot be verified — e.g. 'Use template.md as the fill-in document', '../workshop-facilitation/SKILL.md', 'examples/sample.md', and ~10 'skills/*/SKILL.md' paths. These are multi-level and un-verifiable references with no real bundle to back them, and the SKILL.md itself is a monolithic 600-line document that should be split. Matches the level-1 anchor (deeply nested/unverifiable references, monolithic); not level-2 because there is no actual present-and-clearly-signaled one-level structure to point to.

1 / 3

Total

8

/

12

Passed

Description

82%

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 concrete structural actions, an explicit Use-when trigger, and a distinct niche. The weakest point is trigger-term coverage, which is somewhat narrow and could add common synonyms like 'product requirements' or 'product spec'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'connects problem, users, solution, and success criteria' and 'turning discovery notes into an engineering-ready document' — naming the PRD's constituent parts rather than abstract fluff. Not a level-2 'names domain and some actions' because it enumerates four specific structural components, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' ('Build a structured PRD that connects problem, users, solution, and success criteria') and 'when' via an explicit 'Use when...' trigger ('Use when turning discovery notes into an engineering-ready document for a major initiative'). Matches the level-3 anchor that requires both with an explicit trigger; a missing Use-when clause would cap at 2, but it is present.

3 / 3

Trigger Term Quality

Includes natural terms a PM might say ('PRD', 'discovery notes', 'engineering-ready document', 'major initiative') but misses common variations like 'product requirements', 'product spec', or 'requirements doc'. Not a level-3 'good coverage of natural terms' because the keyword set is narrow, but above level-1 jargon since the terms used are user-facing.

2 / 3

Distinctiveness Conflict Risk

The PRD/requirements-document niche is distinct, with triggers ('discovery notes', 'engineering-ready document', 'major initiative') unlikely to fire for unrelated skills. Matches the level-3 'clear niche with distinct triggers' anchor; not level-2 because it is not merely 'works with document files' generic.

3 / 3

Total

11

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (674 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
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.