product-discovery

Organize continuous product discovery with OST, interviews, and tests.

65|11|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/ericgandrade/claude-superskills --skill product-discovery-ericgandrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/ericgandrade/claude-superskills/tree/main/skills/product-discovery
Command: npx skills add https://github.com/ericgandrade/claude-superskills --skill product-discovery-ericgandrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often run discovery in silos, producing scattered notes and misaligned decisions. This skill creates a living OST-based map that links outcomes, opportunities, and solutions to tests, ensuring evidence drives decisions.

Core Features & Use Cases

  • OST construction and upkeep aligned to measurable outcomes
  • Interview snapshots, not transcripts, for concise evidence
  • Structured assumption testing and solution exploration
  • Weekly discovery cadence and Opportunity Council governance
  • Templates and outputs to synchronize teams across tools

Quick Start

Define your target outcome and run a weekly discovery cycle to generate an OST, interview snapshots, and initial tests.

Frequently Asked Questions about product-discovery

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

FAQPage Schema
How do I organize product discovery using an Opportunity Solution Tree?

To organize product discovery using an Opportunity Solution Tree (OST), this skill links your target outcomes to opportunities, solutions, and assumption tests. It constructs a living OST map that ensures evidence drives your product decisions instead of scattered notes.

What is the best way to document continuous discovery interviews?

The best way to document continuous discovery interviews is by generating concise interview snapshots rather than full transcripts. This skill structures your weekly discovery cadence to capture essential evidence and align it directly within your OST.

How do I test assumptions during product discovery?

To test assumptions during product discovery, this skill applies structured assumption testing and solution exploration within your weekly discovery cycle. It produces test results and templates that connect directly to your mapped opportunities and outcomes.

Can I use this for weekly discovery cadence and Opportunity Council governance?

Yes, you can use this skill to structure a weekly discovery cadence and Opportunity Council governance. It provides ongoing templates and outputs designed to synchronize teams across tools and maintain a continuous, aligned discovery process.

How do I start building an OST for measurable outcomes?

To start building an OST for measurable outcomes, you define your target outcome and run a weekly discovery cycle. This generates your initial OST, interview snapshots, and assumption tests to map opportunities to solutions.