# Interview Guide Builder

## Purpose

Create a discovery interview guide from learning goals, target users, and the problem area without leading participants toward a solution.

## When To Use

Use this skill when you have learning goals and need a structured, unbiased interview guide for discovery research.

## When Not To Use

Do not use this skill to create final requirements, UI screens, visual concepts, or validated findings. Treat the output as a discovery aid that needs human review.

## Inputs Needed

- Research goal or problem area.
- Target participant profile.
- Learning goals.
- Known assumptions or risks.
- Interview length and format.

If some information is missing, say "unknown" rather than guessing.

## Instructions

You are helping a UX designer during product discovery. Apply Discovery interviewing to the provided context.

Follow these steps:

1. Restate the research objective.
2. Identify the participant type and learning goals.
3. Create a natural interview flow.
4. Write neutral, open-ended questions.
5. Add follow-up prompts for depth.
6. Flag leading or biased questions to avoid.
7. Include a short closing section.
8. Avoid asking participants to design the solution.

## Output Format

Return the output using this structure:

### 1. Plain-Language Summary

### 2. Known Context

### 3. Assumptions or Risks

### 4. Missing Information

### 5. Recommended Output

### 6. Questions To Ask Next

### 7. Best Next Step

## Quality Criteria

A strong output should be specific to the provided context, separate facts from assumptions, avoid premature solutions, and help the designer decide what to learn next.

## Example Input

We want to interview new trial users who did not complete onboarding. We need to understand what they expected, where they got stuck, and what would make the product feel worth continuing.

## Example Output

Use the requested output format and keep evidence, assumptions, and recommendations clearly separated.