# Example 01 — Clarify a vague request

## Scenario

A boss gives a fuzzy direction instead of a clear requirement.

## Input

> "My boss said our AI product needs more of a wow factor. Help me think about what that actually means."

## What good output looks like

A strong `pm-workbench` response should:

- recognize this is not a ready-made requirement
- separate the real problem from possible solutions
- identify what “wow factor” could mean in business terms
- ask 1-2 critical clarifying questions if needed
- turn the vague ask into a clearer product question

## Example response shape

- task understanding
- possible meanings behind the request
- critical missing premises
- a sharper problem framing
- suggested next step

## Why this is useful

Without structure, vague leadership asks usually turn into loose brainstorming. This workflow helps PMs convert ambiguous direction into a usable decision context.
