product-discovery

Validate product ideas using JTBD, Kano, and Value Proposition analyses.

258|26|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/majiayu000/claude-arsenal --skill product-discovery-majiayu000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/majiayu000/claude-arsenal/tree/main/skills/product-discovery
Command: npx skills add https://github.com/majiayu000/claude-arsenal --skill product-discovery-majiayu000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validating ideas requires evidence and structured discovery. This Skill covers JTBD, Kano, and Value Proposition practices to guide market research and opportunity assessment.

Core Features & Use Cases

  • JTBD & Jobs stories: Frame problems around customer jobs.
  • Kano & Value Proposition: Classify features by customer impact.
  • Opportunity mapping: Align discovery outcomes with product strategy.

Quick Start

Conduct a brief JTBD interview guide for a new feature and map the findings to a prioritized opportunity tree.

Frequently Asked Questions about product-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a product idea using JTBD and market research?

JTBD (Jobs to Be Done) validation frames problems around what customers are trying to accomplish, not just their stated needs. Conduct structured interviews to uncover the job, map findings to opportunity priorities, and test assumptions against competitive and user data to drive evidence-based decisions.

What's the difference between Kano analysis and Value Proposition Canvas for product discovery?

Kano analysis classifies features by customer impact—basic needs, performance drivers, and delighters—to prioritize development. Value Proposition Canvas aligns features to customer jobs and pains, showing how your offering reduces friction and delivers value relative to alternatives.

How do I structure user interviews for product discovery?

Job stories frame interviews around the context, motivation, and outcome of customer activities rather than generic questions. Guide conversations with open-ended prompts, probe for unmet needs and competing solutions, then synthesize patterns into actionable opportunity maps linked to product strategy.

When should I conduct competitive analysis as part of product discovery?

Competitive intelligence should run parallel to user research to identify market gaps and validate that customer problems are not already solved well. Map competitor positioning against discovered jobs and pain points to sharpen your value proposition and spot underserved opportunities.

Can I use JTBD and Kano methods together in the same discovery workflow?

Yes. Use JTBD interviews to uncover the core jobs and context, then apply Kano to classify which features and solutions your audience views as must-haves, satisfiers, or unexpected delighters, ensuring prioritization reflects both functional need and customer perception.

What assumptions should I test during opportunity assessment?

Test whether customers perceive the problem as urgent, whether your proposed solution addresses the root job, and whether your value proposition is differentiated against alternatives. Evidence-based assumption testing prevents building features for problems that don't drive behavior or revenue.