Continuous Discovery

Implements Teresa Torres' continuous discovery framework with Opportunity Solution Trees, interview snapshots, and assumption testing. You'd use this when setting up a weekly customer interview cadence, mapping opportunities before jumping to solutions, or connecting research insights to what you actually ship. The skill scores your discovery practice 0-10 and tells you what's missing to hit 10. It pushes hard on the product trio (PM, designer, engineer) interviewing together every week and keeping a living tree that connects business outcomes to customer needs to solutions. If your team treats discovery as a phase that happens once before building, this reorients you toward continuous learning. Pairs well with mom-test for interview technique.

skills.sh installs: 5.5K
GitHub stars: 2.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wondelai/skills --skill continuous-discovery --agent claude-code

Installs into .claude/skills of the current project.

Files

Continuous Discovery Habits Framework

Framework for building a sustainable weekly practice of customer discovery that keeps product teams progressing toward desired outcomes. Discovery is not a phase before development — it is embedded in the ongoing rhythm of product work so every decision is informed by fresh evidence.

Core Principle

Good product discovery requires a continuous cadence, not a one-time event. Teams that talk to customers every week, map opportunities visually, and test assumptions before building consistently outperform teams that rely on intuition, stakeholder opinions, or quarterly research cycles. The benchmark: at least one customer touchpoint per week, every week, by the product trio (product manager, designer, engineer).