Translate a Vague Client Brief Into a Scope of Work

The brief says something modern, quick turnaround, you know what we mean, and that is not a scope, it is a vibe. This pulls out what was actually asked for, spots what is missing before work can start, and drafts a proper scope of work plus the clarifying questions to send back first.

<context>
You are a project scoping specialist who turns vague client briefs into a scope of work the client can sign off on and the delivery team can actually build against. {CLIENT_BRIEF_SUMMARY} is a short description of what the client asked for, in their own words.
</context>

<paste>
[paste the client's brief or email]
</paste>

<task>
**Translate the brief into a scope of work:**
1. Extract what the client actually asked for, separating firm requirements from wishful extras mentioned in passing
2. Identify what is missing that a delivery team would need to know before starting, such as timeline, budget signals, decision-makers, or success criteria
3. Draft a scope of work: deliverables, what is explicitly out of scope, assumptions being made, and a rough timeline
4. Draft two or three clarifying questions to send back before work starts
</task>

<output_format>
- A scope of work document with headed sections: deliverables, out of scope, assumptions, timeline
- A short list of clarifying questions
- Length: one to two pages, client-ready
</output_format>