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.

1.50x

Quality

67%

Does it follow best practices?

Impact

98%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/to-prd/SKILL.md

The canonical home for this skill is to-prd in coder/agent-tty

Quality

Content

68%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 content is well-organized, concise, and largely actionable, with a clear process and a useful PRD template. Its main weakness is workflow clarity: publishing to an issue tracker is a one-way, outward-facing action that lacks a verification checkpoint before publishing.

Suggestions

Add an explicit validation/confirmation step before publishing (e.g., 'Review the PRD against the template, then confirm with the user before publishing') to satisfy the destructive/batch feedback-loop requirement.

Reduce the dependency ambiguity by stating how to publish or by making the `/setup-matt-pocock-skills` prerequisite more prominent so the skill is self-contained.

Trim the soft directive ('This list of user stories should be extremely extensive') into a tighter instruction to nudge conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence ('Do NOT interview the user — just synthesize what you already know'), with only minor instances such as the brief 'deep module' aside and soft directives that could be trimmed.	4 / 5
Actionability	Guidance is concrete and specific ('Apply the `needs-triage` triage label', a precise user-story format, explicit exclusions), but minor gaps remain — the issue-tracker publish mechanism is unspecified and the skill depends on external setup context.	4 / 5
Workflow Clarity	Three steps are clearly sequenced with a user-checkpoint, but the publish-to-issue-tracker step is an outward-facing, hard-to-reverse batch action with no validation/verification gate before publishing, capping clarity at 3.	3 / 5
Progressive Disclosure	Good structure with an intro, numbered '## Process' section, and a clearly demarcated <prd-template> with labeled subsections; no bundle files exist, and the inlined template is appropriate, leaving only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly conveys a distinct niche (PRD generation → issue tracker) and answers both what and when, but its action and trigger-term coverage are only moderate. Adding a few concrete actions and natural synonyms would lift specificity and trigger quality.

Suggestions

Expand the action list to mention applying the triage label and structuring the PRD, moving specificity toward comprehensive coverage.

Add natural synonyms such as 'product requirement document' or 'feature spec' alongside 'PRD' to broaden trigger-term coverage.

Tighten the 'Use when' clause to mention additional triggers like writing a feature spec or converting context into a tracked requirement.

Dimension	Reasoning	Score
Specificity	Names the PRD domain with two concrete actions ('Turn the current conversation context into a PRD' and 'publish it to the project issue tracker'), but coverage is not comprehensive — no mention of triage labeling, module sketching, or PRD structure.	3 / 5
Completeness	Both 'what' (turn context into a PRD and publish to the issue tracker) and 'when' ('Use when user wants to create a PRD from the current context') are explicit; the 'when' is concrete but could be richer, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	The natural phrase 'create a PRD' and the acronym 'PRD' are present, but coverage is narrow with no synonyms like 'product requirement document', 'feature spec', or 'spec out'.	3 / 5
Distinctiveness Conflict Risk	The PRD-to-issue-tracker niche is unmistakable with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SnowingFox/ai-skills
Path: .agents/skills/to-prd/SKILL.md
Commit: d6882ad

Reviewed: 23 hours 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.