Product Discovery

This one's for product managers and founders who need to validate ideas before burning engineering time. It enforces hard rules like no solution-first thinking, minimum five user interviews per segment, and evidence-based decisions with clear success metrics. You get frameworks like JTBD, Kano Model, and Value Proposition Canvas, plus Marty Cagan's 10-question opportunity assessment. The weekly continuous discovery structure is solid: customer interviews, assumption testing, and opportunity mapping. Honestly, the strictness around falsifiable assumptions and killing HiPPO-driven features is refreshing. If you're tired of building things nobody wants, this will force the discipline to talk to users first.

skills.sh installs: 313
GitHub stars: 153
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add majiayu000/claude-arsenal --skill product-discovery --agent claude-code

Installs into .claude/skills of the current project.

Files

Product Discovery

Core Principles

Continuous Discovery — Weekly user conversations, not episodic research
Outcome-Driven — Start with outcomes to achieve, not solutions to build
Assumption Testing — Validate risky assumptions before committing resources
Co-Creation — Build with customers, not just for them
Data-Driven — Use evidence over intuition and stakeholder opinions
Problem-First — Deeply understand the problem space before ideating solutions

Hard Rules (Must Follow)

These rules are mandatory. Violating them means the skill is not working correctly.

No Solution-First Thinking

Never start with a solution. Always define the problem and outcome first.

❌ FORBIDDEN:
"We should build a search bar for the product page"
"Let's add AI recommendations"
"Users need a mobile app"

✅ REQUIRED:
"Problem: Users can't find products (40% exit rate on catalog)
Outcome: Reduce exit rate to 20%
Possible solutions:
1. Search bar with filters
2. AI-powered recommendations
3. Better category navigation
4. Visual product browsing"