continuous-discovery

Guides product teams through Teresa Torres's continuous discovery framework with structured workflows.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fahadnari/Claude-skills --skill continuous-discovery-fahadnari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continuous-discovery
Source: https://github.com/fahadnari/Claude-skills/tree/main/continuous-discovery
Command: npx skills add https://github.com/fahadnari/Claude-skills --skill continuous-discovery-fahadnari

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often make build decisions based on opinions, stakeholder requests, or the loudest voice in the room instead of customer evidence. This Skill operationalizes Teresa Torres's Continuous Discovery Habits framework, turning weekly customer touchpoints into structured outcomes, opportunity maps, solutions, and assumption tests. ## Core Features & Use Cases - Outcome Setting: Negotiate measurable product outcomes with leadership using the Outcome Types Hierarchy, pairing performance goals with learning goals. - Opportunity Mapping: Run story-based customer interviews, create interview snapshots, and build a hierarchical Opportunity Solution Tree grounded in real evidence. - Solution Ideation & Assumption Testing: Generate at least three solutions via individual-first ideation, compare them side by side, then identify and test leap-of-faith assumptions before building. - Use Case: A product trio assigned "increase activation" uses the Skill to decompose that into a team-level outcome, interview customers weekly, map 15+ opportunities, select a target opportunity, compare three solutions, and run cheap simulated tests on the riskiest assumptions before committing engineering time. ## Quick Start Ask the assistant to help you set a product outcome, map customer opportunities, ideate solutions, or test assumptions using the continuous discovery framework.

Frequently Asked Questions about continuous-discovery

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

FAQPage Schema
How do I build an Opportunity Solution Tree from customer interviews?▼

Conduct weekly story-based interviews, synthesize each into a one-page snapshot capturing needs, pain points, and desires, then add opportunities to a hierarchical tree under your desired outcome. Continue until you have 10-15 opportunities before prioritizing a target.

What is the continuous discovery framework by Teresa Torres?▼

Continuous discovery is a sustained practice of weekly customer touchpoints by the product trio, using small research activities in pursuit of a desired outcome. It replaces phase-based research with ongoing interviewing, opportunity mapping, solution comparison, and assumption testing.

How do I test product assumptions before building a feature?▼

Break the solution into desirability, viability, feasibility, usability, and ethical assumptions, then map them by importance and evidence. Test leap-of-faith assumptions first using cheap simulated methods like prototypes, fake doors, or one-question surveys with pre-set success criteria.

When should I use A/B testing versus assumption testing?▼

Use A/B tests for optimizing validated solutions, not for discovery. Assumption testing favors faster simulated methods like prototypes, concierge tests, and Wizard of Oz experiments that run in days without writing production code.

What are common continuous discovery mistakes product teams make?▼

Common anti-patterns include accepting output-based goals, asking leading interview questions, mapping solutions as opportunities, evaluating only one solution, testing easy assumptions first, and running discovery as a separate phase from delivery.