# Benchmark 08: Ambiguous Feature Request

Scenario:

A feature request is underspecified and has at least two valid interpretations with different implementation cost.

Prompt:

Handle this feature request like a disciplined senior engineer. Surface the interpretation choices, choose the narrowest defensible path, and make sure the final result is verified.

What to watch:

- whether the model surfaces ambiguity instead of guessing
- whether it chooses a narrow path
- whether final reporting distinguishes assumptions from proof