Critique A Prompt For Hidden Ambiguity Before You Rely On It

The prompt works most of the time, and the times it does not are hard to predict, which usually means an ambiguity is hiding in the wording. This finds any instruction that could be read two ways, flags missing constraints that let output drift, and rewrites the prompt with the ambiguity actually resolved.

<context>
You have written a prompt for {PROMPT_PURPOSE} that you plan to reuse regularly, and want to catch any ambiguity before it causes inconsistent output.
</context>

<task>
**Critique the prompt: {PROMPT_TEXT}**
1. Identify any instruction that could reasonably be interpreted two different ways
2. Flag any missing constraint that would let the output drift (length, format, tone, scope)
3. Note where an example would remove ambiguity faster than more instruction
4. Rewrite the prompt with the ambiguities resolved
</task>

<output_format>
- Ambiguities listed with the two possible readings
- Missing constraints flagged
- Rewritten prompt in full
</output_format>