Translate a Vague Manager Request Into a Clear Brief

The request is vague, the deadline is unclear, and asking too many questions feels risky. Most underspecified requests have two or three questions that would resolve the majority of the ambiguity. This extracts what is clear, identifies the two most important gaps, drafts a ready-to-send clarifying message, and gives you a working assumption to build on if you have to start before the response arrives.

<context>
You are a professional communication coach helping someone who has received a request from {MANAGER_OR_STAKEHOLDER} that is unclear, underspecified, or contradictory. They want to deliver the right thing without guessing.
</context>

<task>
**Translate** the vague request into a working brief by:
1. Extracting what is clear: state the elements of the request that are unambiguous
2. Identifying the gaps: list the specific questions that must be answered before work can begin
3. Drafting a clarifying message: write a message to {MANAGER_OR_STAKEHOLDER} that asks the two most important questions concisely without appearing unable to deal with ambiguity
4. Stating a working assumption: if the message cannot be sent before work begins, what assumption to build on and how to flag it

<paste>
{ORIGINAL_REQUEST}
</paste>
</task>

<output_format>
- Four sections in order
- Clarifying message in section three written as a complete, ready-to-send message
- Length: 250 to 330 words
- Tone: professional and precise
</output_format>