discovery-research-stinger

Organize customer discovery workflows with Opportunity Solution Trees and interview plans.

72|28|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/that-git-life --skill discovery-research-stinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-research-stinger
Source: https://github.com/legioncodeinc/that-git-life/tree/main/.claude/skills/discovery-research-stinger
Command: npx skills add https://github.com/legioncodeinc/that-git-life --skill discovery-research-stinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams avoid building the wrong thing by providing a structured continuous discovery process for understanding customer needs, validating opportunities, and testing assumptions before implementation.

Core Features & Use Cases

  • Continuous Discovery Guidance: Guides teams through desired outcome definition, Opportunity Solution Trees, customer interviews, and weekly discovery workflows.
  • JTBD and Experiment Frameworks: Provides interview structures, assumption mapping methods, and lightweight prototype experiment designs to validate risky ideas.
  • Use Case: A product team unsure what to build next can use this Skill to organize customer insights, identify high-value opportunities, and design experiments before committing engineering resources.

Quick Start

Use the discovery-research-stinger skill to create an Opportunity Solution Tree and interview plan for my product discovery challenge.

Frequently Asked Questions about discovery-research-stinger

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

FAQPage Schema
How do I structure product discovery to avoid building the wrong features?

Product discovery requires structuring customer interviews, mapping assumptions, and validating opportunities before development to avoid building the wrong features. This process uses Opportunity Solution Trees to connect desired outcomes to tested solutions.

What is an Opportunity Solution Tree and how does it guide continuous discovery?

An Opportunity Solution Tree is a framework that maps desired business outcomes to specific customer opportunities and prototype experiments. It guides continuous discovery by visually structuring weekly interview insights into a validated product direction.

How do I design user interviews using Jobs-to-be-Done frameworks?

Jobs-to-be-Done interviews require structuring questions around the specific job a user is hiring a product to do. Design these user interviews by capturing customer needs, mapping underlying assumptions, and validating risky ideas before committing engineering resources.

What is assumption mapping and when should product teams use it?

Assumption mapping is a method to identify and prioritize the riskiest hypotheses underlying a product idea. Product teams should use assumption mapping during discovery to design lightweight prototype experiments that validate risky ideas before development begins.

Can I plan lightweight prototype experiments without dedicated engineering resources?

Yes, you can plan lightweight prototype experiments without engineering resources by structuring discovery workflows around assumption mapping. This approach uses evidence-based guidance and reusable templates to test risky ideas and validate product direction.

What is the best way to prioritize product opportunities before committing to development?

The best way to prioritize product opportunities is by applying a structured continuous discovery process. Teams define desired outcomes, conduct JTBD interviews, and map assumptions to ensure evidence-based validation before committing engineering resources.