The body repeats the description in the Purpose section and the 'Why This Structure Works' / 'Anti-Patterns' sections explain Lean UX concepts Claude already knows; the long examples and pitfalls block could be tightened.

Provides concrete fill-in templates, specific contrastive quality checks (e.g. 'Not "improve the product" but "add one-click Slack notifications..."'), and concrete ✅/❌ examples — fully actionable guidance.

A clear 6-step sequence (Gather Context → Draft → Experiments → Validation → Run & Evaluate → Convert) with explicit decision points and a ✅/❌/⚠️ validation feedback loop in Step 5.

The body references template.md and examples/sample.md, but neither file exists in the bundle, and substantial template/example content is inlined rather than split out; structure is present but the references are dangling.

Names multiple concrete components of the work — 'target user, expected outcome, and validation method' — describing specific actions rather than vague language.

Explicitly answers both what it does (frame an epic as a testable hypothesis) and when to use it ('Use when defining a major initiative before roadmap, discovery, or delivery planning').

Uses natural product-management phrasing a user would say ('defining a major initiative', 'roadmap, discovery, or delivery planning') with good coverage of relevant terms.

Occupies a clear niche — epic-hypothesis framing for product planning — with distinct triggers, third-person voice, and low risk of conflicting with other skills.