common-product-requirements

Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/common/common-product-requirements/SKILL.md

Quality

Content

75%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 lean, well-sequenced instruction skill with concrete directives, a mandatory verification checklist, and clear gating. Its weaknesses are minor: some cross-section redundancy, no explicit post-verification recovery loop, and an unreferenced bundle file plus light duplication between the inline and referenced checklists.

Suggestions

Add an explicit feedback loop after the Verification Checklist (e.g., 'If any box is unchecked, return to Drafting and resolve before handoff') to reach full workflow-clarity anchor 5.

Either reference lean-spec-template.md from the body or remove it from references/ so every bundle file is discoverable and no orphaned asset remains.

Deduplicate the RACI/ownership guidance currently split across the Drafting 'Handoff Quality' bullet, the Anti-Patterns 'Offshore handoff' bullet, and the separate Ownership checklist into a single owned section.

Dimension	Reasoning	Score
Conciseness	The body is dense and terse — short directive bullets with no padding or explanation of concepts Claude already knows — but has minor redundancy (traceability/RACI recur across Drafting, Anti-Patterns, and Ownership checklist), keeping it just below anchor 5.	4 / 5
Actionability	As an instruction-only skill it gives concrete, specific guidance — 'Ask 3-5 clarification questions', 'provide (a, b, c) options', 'Read references/prd-template.md', 'Assign stable REQ-* and AC-* IDs', 'Use Given/When/Then', output to 'docs/prd/prd-[slug].md' — which is mostly executable with only minor gaps, matching anchor 4.	4 / 5
Workflow Clarity	Phases are clearly sequenced (Discovery → Drafting → Verification Checklist) with a mandatory checklist, an Implementation Gate checkpoint, and a discovery 'Repeat until Actionable State' loop; falls short of anchor 5 because there is no explicit error-recovery feedback loop after the verification checklist fails.	4 / 5
Progressive Disclosure	The body is an overview with a References section linking one-level-deep to real files (prd-template.md, checklist.md), but lean-spec-template.md exists in the bundle yet is unreferenced, and the inline Verification Checklist overlaps with the referenced checklist.md — minor organization gaps consistent with anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

78%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 is well-formed: it states a concrete purpose and gives explicit 'Use when' triggers with natural keyword coverage. Its only real limitation is modest action specificity and acknowledged overlap with sibling BRD/SRS skills.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('PRD discovery and drafting') plus the standardized dimensions (scope, user outcomes, requirement IDs, acceptance criteria), but stops at 1-2 actions rather than a comprehensive list, matching anchor 3; not anchor 4 because it lacks several distinct concrete actions.	3 / 5
Completeness	Explicitly answers both what ('Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria') and when ('Use when creating PRD, product requirements, feature specification, or acceptance criteria plan') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'creating PRD', 'product requirements', 'feature specification', 'acceptance criteria' — giving good coverage; falls short of anchor 5 only because it omits common synonyms and file/extension variations.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear PRD/product-requirements niche with distinct triggers, but the body itself acknowledges sibling BRD/SRS skills and routing between them, indicating minor overlap risk with closely related skills — anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: .github/skills/common/common-product-requirements/SKILL.md
Commit: fa8f0ec

Reviewed: 3 days 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.