Skip to content
Skills Library
Management & product · Planning

continuous-discovery

/continuous-discovery

Activate when: a team ships features on opinion instead of evidence; 'we need a discovery habit', 'how often should we talk to users', building a product roadmap; connecting weekly customer contact to decisions. Do NOT activate when: pre-first-customer (use the-mom-test first) or the org has no product to iterate. More: deciqai.com/s/continuous-discovery

Licence
MIT
Last repository change
01.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 01.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Activate when: a team ships features on opinion instead of evidence; 'we need a discovery habit', 'how often should we talk to users', building a product roadmap; connecting weekly customer contact to decisions. Do NOT activate when: pre-first-customer (use the-mom-test first) or the org has no product to iterate. More: deciqai.com/s/continuous-discovery

Triggers from the description

we need a discovery habithow often should we talk to users
Original author description

Activate when: a team ships features on opinion instead of evidence; 'we need a discovery habit', 'how often should we talk to users', building a product roadmap; connecting weekly customer contact to decisions. Do NOT activate when: pre-first-customer (use the-mom-test first) or the org has no product to iterate. More: deciqai.com/s/continuous-discovery

How it works

  1. Overview
  2. When to Use
  3. The Process
  4. Applying It Well
  5. Red Flags
  6. Verification
Original SKILL.md headings · 40 lines, 351 words
SKILL.md preview
---
name: continuous-discovery
description: "Activate when: a team ships features on opinion instead of evidence; 'we need a discovery habit', 'how often should we talk to users', building a product roadmap; connecting weekly customer contact to decisions. Do NOT activate when: pre-first-customer (use the-mom-test first) or the org has no product to iterate. More: deciqai.com/s/continuous-discovery"
---

# Continuous Discovery — Weekly Contact, Opportunity Trees

## Overview
Continuous discovery (Teresa Torres, *Continuous Discovery Habits*, 2021) replaces one-off research with a **weekly cadence of customer touchpoints by the team building the product**, structured around an **opportunity solution tree**: one outcome → the opportunities (unmet needs) that drive it → competing solutions → assumption tests. It keeps roadmaps anchored to real needs instead of the loudest stakeholder.

## When to Use
- A product with users but no steady learning loop
- Roadmap fights decided by seniority, not evidence
- Turning a fuzzy outcome (e.g. "increase activation") into shippable bets

## The Process
1. **Pick one clear outcome** (a behavior/metric, not a feature). *Gate: if the target is a feature, back up to the outcome it serves.*
2. **Interview weekly** — the trio (PM/design/eng), small and continuous, not a quarterly study.
3. **Map opportunities** as a tree under the outcome; keep them as customer needs, not solutions in disguise.
4. **Diverge on solutions** per opportunity (≥3), then converge.
5. **Test the riskiest assumption cheaply** before building (desirability, viability, feasibility, usability).
6. **Prune to the next bet.** *Gate: no assumption test run = you're shipping opinion → stop and test.*

## Applying It Well
- Automate recruiting so weekly interviews actually happen (the habit dies on scheduling friction).
- One opportunity tree per outcome; don't boil the ocean.
- Small continuous samples beat big infrequent ones.

## Red Flags
- Discovery done by a research silo, not the builders.
- Opportunities written as features.
- Interviews stop the moment things get busy.

## Verification
- [ ] Single outcome defined (behavioral)
- [ ] Weekly interview cadence in place
- [ ] Opportunity tree maps needs, not solutions
- [ ] Riskiest assumption tested before build

---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/continuous-discovery** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*

*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/continuous-discovery.json*

Versions

RepositoryScoreLicence
This page · deciqAI/knowledge-skills90MIT
wastedcode/truecast100MIT
wondelai/skills100MIT

Database snapshot: 13.11.2026 · package version a47a40badbdb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90the-mom-test
    Activate when: a founder is about to talk to customers/users to validate an idea; 'I asked people and they loved it', 'how do I run customer interviews', 'is there demand for this?', pre-PMF discovery. Do NOT activate when: the question is quantitative A/B testing on an existing…
  • 100run-continuous-discovery
    Use to keep research a habit, not a phase — small weekly touchpoints with real users, structured as an opportunity-solution tree, with every belief paired to the cheapest test that could break it.
  • 90customer-discovery
    Use when the user says "run customer discovery", "help me interview customers", "write customer interview questions", "validate my assumption", "talk to users", "synthesize customer interviews", "what are my customers saying", "user research for my startup", "mom test…
  • 100prd-v10-continuous-discovery-torres
    Establish weekly customer-discovery cadence and Opportunity Solution Tree practice using Teresa Torres's Continuous Discovery Habits framework during PRD v1.0 Market Adoption. Triggers on requests to set up discovery cadence, build opportunity solution tree, run weekly customer…
  • 100customer-interview
    Plans and scripts customer discovery interviews using The Mom Test. Use when a user wants to plan a customer interview, write discovery interview questions, build an interview script, generate Mom Test questions, or talk to users about a problem. Produces a non-leading question…
  • 100customer-discovery
    Plan customer discovery interviews, write non-leading questions, and analyze notes into evidence. Use when a founder needs to talk to customers, is preparing an interview script, has notes to synthesize, or needs discovery evidence for an application or grant.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.