跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

continuous-discovery

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

wondelai · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add wondelai/skills --skill continuous-discovery

技能说明


name: continuous-discovery description: 'Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.' license: MIT metadata: author: wondelai version: "1.4.0"

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).

Scoring

Goal: 10/10. Score a discovery practice by the seven Quick Diagnostic rows below — start at 3, add 1 point per row answered "yes" (max 10). Bands: 9-10 = weekly cadence, a living Opportunity Solution Tree, systematic assumption testing, and every shipped feature traceable to a customer opportunity; 5-6 = some discovery happening but ad hoc, PM-only, or disconnected from delivery; ≤3 = intuition- and stakeholder-driven with no regular customer contact. Report the current score, the failing rows, and the specific fix for each.

Framework

1. Opportunity Solution Trees

Core concept: An Opportunity Solution Tree (OST) visually connects a desired outcome (top) to customer opportunities (middle) to potential solutions and experiments (bottom), making implicit product thinking explicit and shared.

Why it works: Most teams jump from business outcome straight to solutions, skipping the customer need entirely; the OST forces understanding of the opportunity space first, preventing features nobody wants.

Key insights:

  • Four layers: Outcome > Opportunities > Solutions > Experiments
  • Opportunities are customer needs, pain points, and desires — framed from the customer's perspective
  • The tree is a living artifact, updated weekly as the team learns
  • Break large opportunities into smaller sub-opportunities to make them actionable
  • Pursue multiple opportunities simultaneously — don't bet everything on one

Product applications:

ContextApplicationExample
Quarterly planningMap the opportunity space before committing to features"Increase trial-to-paid conversion" → discover why users don't convert
Feature prioritizationCompare solutions across opportunities for the highest-leverage betThree solutions for "can't find content" vs. two for "confusing onboarding"
Stakeholder alignmentUse the tree as the shared strategy visualWalk leadership through why you chose opportunity X over Y

Ethical boundary: Never cherry-pick opportunities to justify a predetermined solution — the tree must reflect needs discovered through research.

See references/opportunity-trees.md when building or auditing a tree — adds the 4-layer diagram, good-vs-poor outcome tables, solution-generation techniques, a weekly update rhythm, healthy/dying-tree signals, two worked examples, and four anti-patterns.

2. Experience Mapping

Core concept: Current-state experience maps capture how customers accomplish a goal today, step by step, revealing pain points that become opportunities on the tree.

Why it works: Teams assume they understand the customer's current experience; mapping it from interview data exposes gaps, workarounds, and emotions invisible from inside the building.

Key insights:

  • Map the current state, not a future ideal — understand reality first
  • Include actions, thoughts, and feelings at each step
  • Build collaboratively with the full trio, sourced from interview data, not assumptions
  • Experience maps cover the customer's full experience; journey maps cover only your product's touchpoints
  • Pain points and high-emotion moments become OST opportunities

Product applications:

ContextApplicationExample
New problem spaceMap end-to-end before designingHow a small business owner handles invoicing, from creation to chasing payment
Churn analysisMap churned users' experience to find failure pointsUsers abandon onboarding at step 4 — they lack data they need on hand
Cross-functional alignmentBuild the map togetherA three-hour collaborative session produces one shared reference artifact

See references/experience-mapping.md when mapping a new problem space or churn flow — adds the current-state map template, the experience-vs-journey-map distinction, and the collaborative mapping exercise.

3. Interview Snapshots

Core concept: Story-based interviews capture specific past experiences (not opinions or predictions), and each interview is synthesized into a one-page snapshot the whole team can absorb and reference.

Why it works: Customers are poor predictors of their own future behavior; grounding insights in real past events reveals what they ac

阅读完整来源 ↗