# clarify-then-evaluate

## Command intent

Use this command when a request is still fuzzy, but the real downstream question is whether it is worth doing.

## Best fit

- stakeholder asks that arrived half-formed
- leadership requests that sound urgent before they sound clear
- feature ideas that may be interesting but may not deserve a slot

## Workflow chain

1. `clarify-request`
2. `evaluate-feature-value`

## What this command protects

It prevents a weak PM habit:
**evaluating a request that was never properly clarified.**

## What good output looks like

By the end, you should have:

- a cleaner problem statement
- the main missing premise called out
- a go / hold / no-go judgment
- a short rationale you can reuse with the requester

## Example prompt

> First help me clarify this ask, then evaluate whether it is worth doing now. I want a final go / hold / no-go recommendation, not just analysis.
