discovery-interview

Translate vague product ideas into structured specifications via guided discovery interviews.

4|1|Updated Apr 2, 2026

Search Tags:#discovery #interviews #spec-writing #product-spec #research-loops #completeness-check

Ready to run

npx skills add https://github.com/kvokov/oh-my-ai --skill discovery-interview-kvokov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovery-interview
Source: https://github.com/kvokov/oh-my-ai/tree/main/skills/discovery-interview
Command: npx skills add https://github.com/kvokov/oh-my-ai --skill discovery-interview-kvokov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague product ideas and requirements into a concrete, structured product specification with clear decisions, success metrics, and requirements so teams can move forward confidently.

Core Features & Use Cases

Phased discovery flow: Guides orientation, category deep dives, research loops, conflict resolution, and completeness checks before spec writing.
Research enablement: Prompts AskUserQuestion uncertainty options, follows through with WebSearch/WebFetch, and summarizes findings in specs.
Spec generation: Confirms understanding, writes to docs/specs deep file using SPEC_TEMPLATE, and hands off implementation next steps.

Quick Start

Ask the discovery-interview skill to run all seven phases, confirm completeness, and write the resulting spec to docs/specs using SPEC_TEMPLATE.

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 structured specifications?▼

To turn vague product ideas into structured specifications, use a guided discovery interview process. It phases through orientation, deep dives, research loops, and completeness checks to capture decisions, metrics, and requirements for stakeholder alignment.

What is the best way to write a PRD from scratch?▼

The best way to write a PRD from scratch is running a phased discovery interview that captures at least ten questions and resolves conflicts. It confirms understanding and generates the spec using a standardized template in your docs directory.

How do you resolve conflicting requirements during product spec writing?▼

You resolve conflicting requirements during product spec writing through dedicated conflict resolution and research loops. The interview process prompts for uncertainty options and uses web research to summarize findings, ensuring teams document clear decisions.

Can I use a discovery interview for scoping a new build and documenting requirements?▼

Yes, you can use a discovery interview for scoping a new build and documenting requirements. It applies a seven-phase guided flow that translates initial concepts into actionable specs with defined success metrics and implementation next steps.

What are the limitations of automated product spec generation?▼

Limitations of automated product spec generation include the need for active stakeholder participation to answer at least ten questions and perform completeness checks. Without human input during research loops, the resulting spec may lack accurate alignment.