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

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/sdlc/skills/to-prd/SKILL.md

Quality

Content

50%Scale 1-3

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

This skill provides a reasonable workflow for generating PRDs from conversation context, with a useful template and clear process steps. However, it lacks concrete executable guidance for the publishing step, includes some unnecessary conceptual explanation (deep vs shallow modules), and is missing validation checkpoints after the publishing action. The dependency on external setup is acknowledged but not well-handled.

Suggestions

Add explicit validation after publishing to the issue tracker (e.g., confirm issue URL, verify label was applied correctly)

Provide concrete tool usage or commands for publishing to the issue tracker rather than just saying 'publish it'

Remove or significantly trim the deep module definition — Claude already understands this concept; a single sentence reminder is sufficient

Consider extracting the PRD template to a separate file (e.g., PRD_TEMPLATE.md) and referencing it, to keep the main skill leaner

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary explanation, such as the definition of 'deep module' which Claude already understands. The PRD template is appropriately detailed for its purpose, though the user-story example could be trimmed.	2 / 3
Actionability	The process steps are clear and the PRD template provides concrete structure, but there are no executable commands or code examples for publishing to the issue tracker. Key details like how to actually publish or which tool/API to use are missing, relying on external setup.	2 / 3
Workflow Clarity	The 3-step process is clearly sequenced with a user checkpoint in step 2, but there's no validation after publishing to the issue tracker (e.g., confirming the issue was created successfully, verifying the label was applied). The workflow also has an implicit dependency on `/setup-matt-pocock-skills` without clear error handling if that hasn't been run.	2 / 3
Progressive Disclosure	The PRD template is inline which is reasonable given no bundle files exist, but the template is quite long and could potentially be extracted to a separate file. The reference to `/setup-matt-pocock-skills` and external issue tracker/triage label vocabulary is mentioned but not clearly signaled with navigation links.	2 / 3
	Total	8 / 12 Passed

Description

67%Scale 1-3

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 adequately covers the what and when, earning full marks on completeness. However, it describes only a single action without detailing sub-capabilities, and its trigger terms lack natural variations that users might employ (e.g., 'product requirements document', 'spec'). The description is functional but could be more specific and distinctive.

Suggestions

Add natural trigger term variations such as 'product requirements document', 'product spec', 'requirements doc', 'spec document' to improve discoverability.

List more specific concrete actions like 'generates PRD sections including goals, user stories, acceptance criteria, and timeline, then publishes to the issue tracker'.

Specify the issue tracker type or add distinguishing details (e.g., 'Linear', 'Jira', 'GitHub') to reduce potential overlap with other issue-creation skills.

Dimension	Reasoning	Score
Specificity	It names a specific action ('Turn the current conversation context into a PRD and publish it to the project issue tracker'), but only describes one action rather than listing multiple concrete capabilities like formatting options, templates, or specific PRD sections.	2 / 3
Completeness	Clearly answers both what ('Turn the current conversation context into a PRD and publish it to the project issue tracker') and when ('Use when user wants to create a PRD from the current context'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes 'PRD' and 'issue tracker' as relevant keywords, but misses natural variations users might say like 'product requirements document', 'product spec', 'requirements doc', 'write a PRD', or specific tracker names like 'Jira', 'Linear', 'GitHub issues'.	2 / 3
Distinctiveness Conflict Risk	The combination of PRD creation and issue tracker publishing is somewhat distinctive, but 'publish it to the project issue tracker' is vague enough that it could overlap with other issue-creation or documentation skills. Specifying the tracker type or PRD format would improve distinctiveness.	2 / 3
	Total	9 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: whimzyLive/nightshift-ai
Path: plugins/sdlc/skills/to-prd/SKILL.md
Commit: 8a737ca

Reviewed: about 8 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.