discovery-interview

Identify user needs and constraints through structured iterative interviews.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/yao-agent-skills --skill discovery-interview-firstsun-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-interview
Source: https://github.com/firstsun-dev/yao-agent-skills/tree/main/external/career/interview/discovery-interview
Command: npx skills add https://github.com/firstsun-dev/yao-agent-skills --skill discovery-interview-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep interviews transform fuzzy ideas into actionable specifications by surfacing hidden assumptions, aligning stakeholders, and guiding precise scope.

Core Features & Use Cases

  • Structured, phase-driven interview process that uncovers requirements, constraints, and tradeoffs.
  • Cross-functional applicability for both technical and non-technical audiences, enabling rapid alignment and documented decisions.
  • Production-ready outputs including a clear problem statement, goals, and a traceable spec scaffold.

Quick Start

Begin an interview by asking the user to summarize the problem in one sentence, identify the target users, and confirm whether this is a new idea or an improvement.

Frequently Asked Questions about discovery-interview

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

FAQPage Schema
How do I turn vague product ideas into actionable specifications?

Structured discovery interviews transform vague product ideas into actionable specifications by surfacing hidden assumptions, aligning stakeholders, and guiding precise scope across problem framing, goals, and technical landscape.

What is the best way to gather requirements from both technical and non-technical stakeholders?

A structured, phase-driven interview process enables requirement gathering from both technical and non-technical stakeholders by guiding exploration across UX, data, and constraints to capture documented decisions and tradeoffs.

How do I start a discovery interview for product design?

Start a discovery interview by asking the user to summarize the problem in one sentence, identify target users, and confirm whether this is a new idea or an improvement to an existing system.

What should a product specification include to ensure reliable handoffs and traceable execution?

A product specification for reliable handoffs and traceable execution should include a clear problem statement, goals, documented decisions, research needs, tradeoffs, and acceptance criteria derived from iterative stakeholder interviews.

Can I use a structured interview process to capture technical constraints and tradeoffs?

Yes, a structured interview process captures technical constraints and tradeoffs by guiding exploration across the technical landscape and documenting uncertainties to enable reliable handoffs and traceable execution.

When do I need a phase-driven interview to produce an implementable specification?

You need a phase-driven interview to produce an implementable specification when transforming fuzzy ideas into documented decisions, aligning cross-functional teams, and defining precise scope and acceptance criteria for execution.