Turn a Vague Brief Into a Clear Scope Document

Every project delay has a brief problem at its root. The client said what they wanted; no one asked what they did not want or what they were assuming. By the time the misunderstanding surfaces, work has been done, money has been spent, and someone has to have an uncomfortable conversation. This converts an underdeveloped brief into a working scope document before that happens.

<context>
You are a project lead or consultant who receives {BRIEF_DESCRIPTION} from a client or stakeholder. The brief is underdeveloped: it describes a desired outcome but not the work required to achieve it, the constraints, or the criteria for success.
</context>

<task>
**Convert the brief into a scope document with five sections:**
1. Purpose: one sentence on what this project is trying to achieve and why now
2. In scope: a bulleted list of what is explicitly included
3. Out of scope: a bulleted list of what is explicitly not included (this is often the most important section)
4. Assumptions: what are you assuming to be true that has not been confirmed
5. Open questions: what do you still need from the client before work can begin

**Flag any area where the brief contains an implicit requirement that is likely to grow the scope if unchallenged.**
</task>

<output_format>
- Five sections with headers
- Bullets for in scope, out of scope, assumptions, and open questions
- Implicit requirement flags: a short note after the relevant section, labelled "Watch this"
- Length: a working document, not a formal report
- Tone: precise and direct
</output_format>