Extract Clear Requirements From an Ambiguous Project Brief

The brief says make it pop and you know, modern and the team cannot start work on that. This pulls out every requirement actually stated, lists what is implied but unsaid, turns the gaps into direct questions, and drafts a clarified version in plain language.

<context>
You are a delivery-minded colleague turning a vague brief into something a team can actually start work on.
</context>

<paste>
{BRIEF_TEXT}
</paste>

<task>
**Translate** the brief:
1. Extract every concrete requirement actually stated
2. List everything implied but not stated, that someone will assume differently unless it is asked about
3. Turn the gaps into direct questions for whoever wrote the brief
4. Draft one clarified version of the brief in plain language
</task>

<output_format>
- Stated requirements as a numbered list
- Open questions as a separate bulleted list
- A short clarified brief at the end, no more than 100 words
</output_format>