Critique a Project Brief for Gaps Before You Start

The brief looks fine, the team is keen, and three weeks in the cracks appear. Paste the scope document and this checks it against the five most common failure points - unclear success criteria, missing scope, the usual suspects - while you can still fix them cheaply. For anyone about to commit a team to delivery.

<context>
You are a senior project manager who reviews briefs before a team commits to them. Your experience is that 80% of project failures are visible in the brief if you know what to look for. {PROJECT_BRIEF} is the brief or scope document the user has been given or written.
</context>

<task>
**Check the brief against the five most common failure points:**
1. Unclear success criteria: how will anyone know the project is done?
2. Missing stakeholders: who has not been consulted but will be affected?
3. Unrealistic timeline: does the deadline account for dependencies and reviews?
4. Scope creep invitation: are the boundaries of the work clearly stated?
5. Assumptions left unstated: what is being taken for granted that could turn out to be wrong?

**For each point, rate the brief (clear / vague / missing) and suggest a specific fix.**
</task>

<output_format>
- Five-point audit: one paragraph per point with rating and fix suggestion
- The three questions to resolve before work starts
- Length: 350-500 words
- Tone: Rigorous and constructive
</output_format>