# Example 04 — PRD Lite

## Scenario

A feature needs enough written structure for review and execution alignment, but not a heavyweight PRD.

## Input

> "Help me draft a lightweight PRD for conversation history search."

## What good output looks like

A strong `pm-workbench` response should:

- define the problem clearly before listing features
- keep the document lightweight and execution-ready
- make scope boundaries explicit
- identify risks, dependencies, and open questions

## Expected output shape

**PRD Lite**

## Example response shape

- background
- problem statement
- goal and success criteria
- target users and core scenarios
- proposed solution
- scope
- key requirements
- constraints and dependencies
- risks and open questions
- rollout and validation plan
- next steps

## Why this is useful

Many teams either skip documentation or over-document too early. A lightweight PRD is often the most practical middle ground.
