continuous-discovery

Implement weekly customer discovery processes with opportunity solution tree mapping.

389|121|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/menkesu/awesome-pm-skills --skill continuous-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continuous-discovery
Source: https://github.com/menkesu/awesome-pm-skills/tree/main/continuous-discovery
Command: npx skills add https://github.com/menkesu/awesome-pm-skills --skill continuous-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly discovery habits help product teams stay connected to customers and make evidence-based decisions, preventing build-first errors.

Core Features & Use Cases

  • Core Frameworks: Continuous Discovery Habits, Product Trio, Opportunity Solution Trees
  • Artifacts: Interview Snapshots, Assumption Testing, OS Tree updates
  • Use Case: Planning weekly research, mapping opportunities, testing assumptions before building.

Quick Start

Kick off by forming a product trio, set one clear outcome, and schedule your first three customer interviews.

Frequently Asked Questions about continuous-discovery

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

FAQPage Schema
How do I set up weekly customer discovery habits for my product team?▼

Continuous discovery requires a product trio, a defined outcome, and living artifacts like interview snapshots and opportunity solution trees to guide weekly product decisions. You need cross-functional commitment before starting.

How do I map an opportunity solution tree during product discovery?▼

Map opportunity solution trees by updating them weekly with interview snapshots gathered during customer discovery. This ensures your product trio aligns opportunities and tests assumptions against a defined outcome.

What is the product trio model for continuous discovery?▼

The product trio model brings together product, design, and engineering to conduct weekly customer interviews, map opportunity solution trees, and test assumptions collaboratively for evidence-based product decisions.

How to test assumptions before building a product feature?▼

Test assumptions before building by running weekly discovery interviews, creating interview snapshots, and updating your opportunity solution tree to validate specific hypotheses with your product trio.

When should I not use continuous discovery habits?▼

Avoid continuous discovery if you cannot commit a product trio to weekly interviews or lack a defined business outcome, as living artifacts like opportunity solution trees require consistent weekly updates.