CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-prd

Writes a short PRD in prds/<slug>.md before non trivial work: problem, root cause for bugs, proposed solution, files to change, edge cases, verification steps, and a completion log, with UTC metadata. Then queues the work in task.md. Use before any multi file feature, schema change, architectural decision, or bug that took real investigation, or when the user says write a PRD, @create-prd, or plan this.

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary instruction-only skill: tight, unambiguous, and fully actionable, with a clear when/skip gate, exact naming and location rules, a sequenced post-writing workflow with validation gates, and a properly separated one-level reference holding the full template. No dimension shows meaningful weakness.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — no concept explanations, no padding; lines like "Get the time from the system… Never invent it" and "The completion log is append only" assume competence and every token instructs.

5 / 5

Actionability

Concrete, executable guidance throughout: exact path pattern "prds/<feature-or-problem-slug>.md" with a worked example, the copy-paste command `date -u +"%Y-%m-%d %H:%M UTC"`, specific task.md integration ("under ## To Do as checkable items, with the PRD path"), and a full copy-paste template in the reference file.

5 / 5

Workflow Clarity

"After writing it" gives a numbered sequence with explicit checkpoints ("Wait for an answer on that choice", "Start building only once the plan is clear"), and validation is enforced via "Each verification step has an expected result" and the Never rule "Mark it Done before its verification steps ran".

5 / 5

Progressive Disclosure

Clear sectioned overview with a single well-signaled, one-level-deep reference — "Copy the full template from [references/prd-template.md](references/prd-template.md)" — which exists and contains the full template; the body keeps only the skeleton and filling guidance, an appropriate split.

5 / 5

Total

20

/

20

Passed

Description

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

A strong description: concrete, third-person, and explicit about both capabilities and triggering conditions, with named file locations and output artifacts. The only weaknesses are a couple of missing natural synonyms and the slightly generic "plan this" trigger that could collide with other planning skills.

DimensionReasoningScore

Specificity

"Writes a short PRD in prds/<slug>.md" with an enumerated list of PRD parts ("problem, root cause for bugs, proposed solution, files to change, edge cases, verification steps, and a completion log, with UTC metadata") plus "queues the work in task.md" — multiple concrete actions with comprehensive coverage, in third person.

5 / 5

Completeness

Explicitly answers what ("Writes a short PRD… Then queues the work in task.md") and when ("Use before any multi file feature, schema change, architectural decision, or bug that took real investigation, or when the user says write a PRD, @create-prd, or plan this") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("write a PRD", "@create-prd", "plan this", "multi file feature", "schema change", "architectural decision"), but common synonyms like "spec", "product requirements doc", or "requirements" are absent.

4 / 5

Distinctiveness Conflict Risk

The PRD-writing niche is clear with distinct triggers ("write a PRD", "@create-prd"), but the generic trigger "plan this" and "before any multi file feature" create minor overlap risk with general planning or scaffolding skills.

4 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

waynesutton/convexskills

Path

skills/create-prd/SKILL.md

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.