epic-hypothesis

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/epic-hypothesis/SKILL.md

Quality

Content

70%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 offers a clear, well-sequenced workflow with strong actionability and an explicit validation decision point. Its weaknesses are verbosity (duplicated intent, conceptual exposition Claude already knows) and broken references to bundle files that are not actually present.

Suggestions

Trim the Purpose section (it duplicates the intent frontmatter) and the "Why This Structure Works" list, which states Lean UX concepts Claude already knows.

Either add the referenced `template.md` and `examples/sample.md` under references/ (or assets/) or inline their content so the deferred material is actually reachable.

Consolidate the repeated per-step "Quality checks" lists into a single quality-bar reference to reduce token overhead without losing the criteria.

Dimension	Reasoning	Score
Conciseness	The Purpose section repeats the intent verbatim, "Why This Structure Works" states Lean UX concepts Claude already knows, and per-step quality-check lists pad the length, though the core guidance remains useful.	3 / 5
Actionability	Concrete fill-in templates, named experiment types (concierge, Wizard of Oz, landing page), and ✅/❌ worked examples give specific actionable guidance, though the templates stay placeholder-level and full examples are deferred.	4 / 5
Workflow Clarity	Six numbered Steps run Gather Context → Draft → Experiments → Validation Measures → Run & Evaluate → Convert, and Step 5 gives an explicit validated/invalidated/inconclusive decision checkpoint with a retry feedback loop.	5 / 5
Progressive Disclosure	SKILL.md is well-sectioned and signals `template.md` and `examples/sample.md`, but no references/ or assets/ bundle files exist, so those referenced paths are missing and the deferred content is unreachable.	3 / 5
	Total	15 / 20 Passed

Description

83%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 that clearly states both the capability and a concrete Use-when trigger, with good specificity and trigger-term coverage. The main gap is slightly less comprehensive synonym coverage and a degree of breadth in the trigger that could overlap related PM skills.

Dimension	Reasoning	Score
Specificity	"Frame an epic as a testable hypothesis with target user, expected outcome, and validation method" names several specific concrete components of the artifact rather than a single generic action.	4 / 5
Completeness	It explicitly answers both what ("Frame an epic as a testable hypothesis...") and when ("Use when defining a major initiative before roadmap, discovery, or delivery planning") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"defining a major initiative" and "before roadmap, discovery, or delivery planning" give good keyword coverage of natural PM planning triggers, though some synonyms (epic, bet, experiment) are absent.	4 / 5
Distinctiveness Conflict Risk	"testable hypothesis" framing for a major initiative is a clear niche, though "defining a major initiative" is broad enough to risk minor overlap with adjacent discovery/roadmap skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/epic-hypothesis/SKILL.md
Commit: 1b5a524

Reviewed: 4 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.