← ClaudeAtlas

continuous-discovery-habitslisted

Product discovery framework based on Teresa Torres' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing assumption tests before committing to a feature, (4) writing or critiquing interview snapshots from customer conversations, (5) generating multiple solution candidates for an opportunity (especially with How Might We), (6) mapping a current-state customer experience or journey to surface unmet needs, (7) diagnosing why a product team is shipping without moving outcomes, (8) running a discovery pre-mortem before committing to a solution branch, (9) building or strengthening a weekly customer-interview habit, (10) connecting business outcomes to product outcomes to opportunities to solutions in a single coherent tree.
tomaszstaniak/pm-ai-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill tomaszstaniak/pm-ai-skills
# Continuous Discovery Habits A structured, repeatable approach to product discovery that helps teams make better product decisions through weekly customer touchpoints, opportunity mapping, and rapid assumption testing. Based on Teresa Torres' "Continuous Discovery Habits." ## Core Principle **Good product teams don't debate opinions — they test assumptions.** The goal of discovery is not to validate ideas, but to discover opportunities and find the best path to a desired outcome. Discovery is not a phase; it is a continuous, weekly habit embedded into how teams work. The foundation: most product teams skip discovery entirely, jumping from a business outcome directly to a solution. The Opportunity Solution Tree (OST) provides the missing structure — it forces teams to explore the problem space before committing to solutions, and to compare multiple solutions against clear criteria before building anything. ## Scoring **Goal: 10/10.** When reviewing product discovery work, rate it 0-10: | Score | Description | |-------|-------------| | 0-2 | No discovery. Team builds what stakeholders request or what feels right. No customer contact. | | 3-4 | Sporadic discovery. Occasional user research, but not connected to decisions. Ideas come from inside the building. | | 5-6 | Some structure. Team talks to customers but lacks a systematic way to prioritize opportunities or test assumptions. | | 7-8 | Strong discovery. OST exists, weekly customer touchpoints, assumption testing bef