# Research Question Generator

## Purpose

Turn a problem area into stronger discovery research questions, with weaker or leading questions flagged before research begins.

## When To Use

Use this skill when you know the problem area but need sharper research questions before choosing methods or writing an interview guide.

## 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

- Problem area or draft problem statement.
- Target users or segments.
- Business goal or product decision to inform.
- What the team already knows, assumes, or needs to learn.

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

## Instructions

You are helping a UX designer during product discovery. Apply Research planning to the provided context.

Follow these steps:

1. Restate the problem area.
2. Identify what the team needs to learn before designing.
3. Generate primary discovery research questions.
4. Generate supporting secondary questions.
5. Flag leading, solution-shaped, or overly broad questions.
6. Suggest suitable research methods.
7. Avoid questions that assume the cause of the problem.

## 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 think new users are dropping off during onboarding, but we do not know whether the issue is setup time, unclear value, missing guidance, or lack of trust.

## Example Output

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