continuous-discovery-cadence

Establishes a weekly continuous discovery rhythm of customer touchpoints, opportunity revisits, and assumption tests.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill continuous-discovery-cadence-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continuous-discovery-cadence
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/continuous-discovery-cadence
Command: npx skills add https://github.com/hero-engine/hero --skill continuous-discovery-cadence-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often treat discovery as an episodic research sprint, so customer insight decays between bursts and specs get written without evidence. This Skill operationalizes Teresa Torres-style continuous discovery as a recurring weekly habit that keeps the Opportunity Solution Tree fed with fresh evidence. ## Core Features & Use Cases - Weekly Cadence Design: Defines the minimum rhythm of three customer touchpoints, one opportunity revisit, and one assumption test per week, plus a 1-hour-per-week minimum viable version. - Recruitment Loop Setup: Provides a standing pipeline for sourcing research participants through always-on signup, self-booking schedulers, and sales/CS handoffs. - Synthesis and OST Integration: Turns raw interview notes into user-voice opportunity statements with evidence attribution that flow into the Opportunity Solution Tree and onward into PRD evidence sections. - Use Case: A PM starting a discovery practice from zero uses this Skill to set up a Tuesday/Thursday interview slot, synthesize each conversation into the OST weekly, and ensure validated opportunities reach authored specs. ## Quick Start Ask the agent to set up a continuous discovery cadence for your team, including weekly touchpoints, a recruitment loop, and OST synthesis.

Frequently Asked Questions about continuous-discovery-cadence

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

FAQPage Schema
How do I set up a continuous discovery habit for my product team?▼

Commit to a weekly rhythm of three customer touchpoints, one opportunity revisit, and one assumption test. If time is limited, start with the 1-hour version: 20 minutes of customer conversation, 20 minutes of synthesis, and 20 minutes updating the Opportunity Solution Tree.

What is the minimum viable customer discovery cadence?▼

The floor is one hour per week split across a single customer touchpoint, synthesis of findings, and an OST revisit. Recurrence matters more than volume; three touchpoints weekly for a quarter beats thirty in one month followed by nothing.

How do I recruit customers for weekly discovery interviews?▼

Build a standing recruitment loop: an always-on signup page, a self-booking calendar link with fixed weekly slots, automated thank-yous with 90-day rotation, and a weekly feed from sales and support. The pipeline should be full enough that the question is which conversation is most useful, not whether anyone is available.

What is the difference between intake and continuous discovery?▼

Intake is reactive, capturing inbound feedback that arrives on its own, while discovery is proactive research that seeks out what customers are not saying. Intake clusters feed discovery opportunities, and the OST in turn prioritizes which intake clusters get attention.

Why does a continuous discovery cadence break down?▼

Cadence erodes through specific failure modes: empty recruitment pipelines, unsynthesized interview notes, OST updates without assumption tests, or discovery output that never reaches authored specs. Identify the first broken link and patch that stage rather than restarting the whole practice.