CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-prd

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Quality

68%

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

Quality

Content

63%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 dense, genuinely actionable process skill — exact template, exact command, worked examples for every PRD section, and well-placed user checkpoints. Its costs are prose that is often more cryptic than its content warrants and a fully monolithic layout with no reference files, which makes the long template unavoidable inlined weight.

Suggestions

Move the PRD template (Objective through Further Notes, ~125 lines) into references/prd-template.md and keep a short summary of each section's rule in SKILL.md, loading the template only at write time.

Rewrite the grilling-conversation bullet as a short decision list (grilled? → yes / no / nobody to answer) instead of a ten-line dense paragraph; the same tightening applies to phrases like "A section is a menu item, not a form field".

Drop the generic Implementation Decisions capability list ("The modules that will be built/modified... Architectural decisions") in favor of the one rule that filters entries — the penalty-for-being-wrong test already stated above it.

DimensionReasoningScore

Conciseness

The skill doesn't explain concepts Claude already knows — every rule is kit-specific — but several passages could be tightened: the ten-line grilling bullet buries a simple yes/no gate in dense prose ("A run with nobody to answer — spawned by another session, or unattended — takes the No path without asking"), and the Implementation Decisions list of generic capability bullets adds little. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4's 'minor instances'.

3 / 5

Actionability

The guidance is highly concrete for an instruction-only skill: a copy-paste trace command with no-op handling ("sh scripts/trace.sh emit kind=prd.write ... || :"), exact EARS syntax forms, and worked examples for scenarios, requirements, and living-spec deltas. Minor gaps — "Explore the repo to understand the current state" and tracker discovery depend on external files — keep it below the fully-specified anchor 5.

4 / 5

Workflow Clarity

A clear sequence runs from pre-flight checks (factory deferral, the one grilling question) through a numbered four-step process to publication, with real checkpoints: "Check with the user that these seams match their expectations", "reread it as a stranger", and recording the publish once the tracker numbers it. It lacks the explicit validate-fix-retry feedback loops of anchor 5, but no destructive or batch operation is involved.

4 / 5

Progressive Disclosure

There are no bundle files at all — references/, scripts/, and assets/ are absent — and the skill is one monolithic document with the ~125-line PRD template fully inlined. Section headers and the <prd-template> delimiters give it structure, but content that could live in a reference file is all inline, matching 'some structure but could be better organized' rather than 4's 'most content is appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

62%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 answers both what and when in third person with a distinct PRD niche, but its trigger vocabulary is thin — it leans entirely on the single token "PRD" with no synonyms, and the when clause merely mirrors the what. Adding concrete trigger phrases and a hint of the PRD's shape would lift it.

Suggestions

Add natural synonyms and trigger phrases to the 'when' clause, e.g. "Use when the user asks for a PRD, product requirements document, requirements doc, or spec from the current conversation".

Broaden the what beyond two actions — mention that it synthesizes the conversation without interviewing, follows a PRD template, and publishes to the tracker with an autonomy label.

Spell out "PRD (product requirements document)" at least once so users who say "requirements doc" or "spec" still trigger the skill.

DimensionReasoningScore

Specificity

Names two concrete actions — "Turn the current conversation context into a PRD" and "publish it to the project issue tracker" — but stops there, with no coverage of what the PRD contains or how publication works. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions.

3 / 5

Completeness

Both parts are present: the what ("Turn the current conversation context into a PRD and publish it to the project issue tracker") and an explicit when ("Use when user wants to create a PRD from the current context"). The when clause is circular — it restates the what rather than giving concrete trigger phrases — so it falls short of anchor 5.

4 / 5

Trigger Term Quality

"PRD" and "create a PRD" are natural terms a user would say, but the description offers no synonyms or variations — no "product requirements document", "requirements doc", or "spec". This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The PRD-from-conversation niche with tracker publication is clearly distinct, though the description could overlap with adjacent planning/ticketing skills in the same kit. 'Mostly distinct; minor overlap risk with closely related skills' is the best fit.

4 / 5

Total

14

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 possibly missing (FACTORY.md)

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/trace.sh)

Warning

Total

12

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/to-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.