product-discovery

Name: product-discovery
Availability: InStock
Author: viethahong

Identify customer problems and validate product ideas through structured discovery.

2|Updated Apr 25, 2026

Search Tags:#validation #prototype #risk-management #jobs-to-be-done #user-research #product-discovery

Ready to run

npx skills add https://github.com/viethahong/business-skills --skill product-discovery-viethahong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/viethahong/business-skills/tree/main/skills/product/product-discovery
Command: npx skills add https://github.com/viethahong/business-skills --skill product-discovery-viethahong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams often build features without validating demand, leading to wasted resources. This skill guides teams through a repeatable discovery process to uncover real problems and validate concepts before heavy development.

Core Features & Use Cases

Risk & Hypothesis Identification: Catalogs Value, Usability, Feasibility, and Viability risks.
User Research & JTBD Mapping: Designs interviews to uncover Jobs-to-be-done and customer pain points.
Solution Ideation & Prototyping: Generates multiple approaches and quick prototypes to test hypotheses.
Synthesis & Decision: Provides structured outputs to decide Build, Pivot, or Kill.
Use Case: For a new feature, run a discovery sprint to determine whether customers would adopt a crypto payment or a new onboarding flow.

Quick Start

Run a structured discovery session to identify customer problems, validate ideas, and produce a prioritized MVP plan.

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 before committing development resources?▼

To validate a product idea before development, run structured product discovery to identify real customer problems and test concepts. This process catalogs Value, Usability, Feasibility, and Viability risks to guide your build decisions.

What is the best way to uncover customer pain points using Jobs-to-be-Done?▼

The best way to uncover customer pain points using Jobs-to-be-Done is by designing targeted user research interviews. This JTBD mapping approach reveals the core jobs customers are trying to accomplish and highlights friction points across market contexts.

How do I run a product discovery sprint for a new feature?▼

To run a product discovery sprint for a new feature, execute a structured workflow covering user research, JTBD analysis, risk assessment, and rapid prototyping. This produces a prioritized MVP plan to determine whether customers would adopt the feature.

How do I decide whether to build, pivot, or kill a product prototype?▼

To decide whether to build, pivot, or kill a product prototype, synthesize user research and hypothesis testing outputs. Structured discovery provides evidence-based synthesis from rapid prototyping workflows to guide your final product decisions.

Can I use rapid prototyping to test multiple solution approaches?▼

Yes, you can use rapid prototyping to test multiple solution approaches. This product discovery process generates diverse approaches and quick prototypes to validate hypotheses and mitigate usability and feasibility risks early.

What risks should I assess during early stage product discovery?▼

During early stage product discovery, you should assess Value, Usability, Feasibility, and Viability risks. Identifying these risks catalogs potential failure points and ensures your MVP planning addresses critical business and technical hypotheses.