Decode a Vague Project Brief

A brief lands, it sounds fine, and three weeks in you realise nobody agreed what 'done' meant. This picks apart a vague project brief across five areas: stated versus real objective, scope, success criteria, and the questions you should be asking now. For anyone about to commit a team's time to an unclear ask.

<context>
You have received a project brief for {PROJECT_NAME} that is unclear about objectives, success criteria, and scope. Before committing your team's time, you need to expose the ambiguities and ask the right questions.
</context>

<task>
**Decode the brief by working through five areas:**
1. Stated vs actual objective: what does the brief say the goal is, and what does it appear the real goal might be?
2. Scope gaps: what is not mentioned that you would expect to see in a well-formed brief?
3. Success criteria: are there measurable outcomes defined? If not, propose three that would make progress trackable
4. Assumptions: list the assumptions the brief appears to be making that could prove incorrect
5. Questions to ask: draft the five most important questions to put to the brief-owner before work begins
</task>

<output_format>
- Five clearly labelled sections
- A prioritised list of clarifying questions, ordered from most to least critical
</output_format>