continuous-discovery

Build weekly customer discovery habits using Opportunity Solution Trees, interviews, and assumption testing.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill continuous-discovery-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-discovery
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/continuous-discovery
Command: npx skills add https://github.com/HafidJoss/Lummy --skill continuous-discovery-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often build features based on intuition, stakeholder opinions, or stale research, resulting in products nobody uses. This Skill establishes a sustainable weekly cadence of customer touchpoints so every product decision is grounded in fresh evidence. ## Core Features & Use Cases - Opportunity Solution Trees: Visually connect business outcomes to customer opportunities, solutions, and experiments, keeping strategy explicit and shared. - Story-Based Interviews & Snapshots: Run weekly customer interviews using past-behavior questions and synthesize each into a one-page snapshot the whole trio can reference. - Assumption Testing & Prioritization: Map desirability, viability, feasibility, and usability assumptions on an importance-vs-evidence grid, test the riskiest ones cheaply, and compare opportunities head-to-head. - Use Case: A product trio assigned to improve trial-to-paid conversion uses this Skill to set up automated interview recruitment, build an OST from interview evidence, test the riskiest assumption with a painted-door experiment, and ship a validated solution. ## Quick Start Help me set up a weekly continuous discovery practice for my product trio, starting with an Opportunity Solution Tree for our retention outcome.

Frequently Asked Questions about continuous-discovery

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

FAQPage Schema
How do I start continuous discovery habits on a product team?

Start with one customer interview per week attended by the full product trio (PM, designer, engineer). Automate recruitment with in-app intercepts and scheduling tools, block a recurring calendar slot, and complete a one-page interview snapshot immediately after each session.

What is an Opportunity Solution Tree and how do I build one?

An Opportunity Solution Tree is a four-layer visual connecting a measurable outcome to customer opportunities, solutions, and experiments. Define a measurable outcome first, populate opportunities from interview evidence, break large opportunities into sub-opportunities, then generate multiple solutions per opportunity.

How do I test assumptions before building a feature?

List the desirability, viability, feasibility, and usability assumptions behind the solution, then map them on an importance-vs-evidence grid. Test high-importance, low-evidence assumptions first with cheap fast tests like painted-door buttons, one-question surveys, or Wizard of Oz prototypes, with success criteria defined upfront.

What questions should I ask in customer discovery interviews?

Ask about specific past behavior rather than opinions or predictions, using the anchor question "Tell me about the last time you..." followed by sequence, clarification, and emotion questions. Avoid leading questions, hypothetical scenarios, and pitching your solution during the interview.

How many customer interviews per week should a product team do?

The minimum viable cadence is one interview per week with the full product trio present, plus 10-15 minutes of snapshot synthesis afterward. As the habit matures, scale to two or three weekly interviews covering active users, churned users, and prospects.

When should I pivot away from a prioritized opportunity?

Pivot when assumption tests consistently fail, new interviews reveal a bigger opportunity, or the target outcome is not moving despite shipped solutions. One failed test is not enough; look for a pattern of failures and confirm you actually tested assumptions before building.