Summarise a Project for Someone Who Missed Most of It

At some point a stakeholder or new team member needs to understand a project they have not been part of. The alternative to a good brief is a long call that rehashes everything or a document no one reads. This produces a concise, structured summary that covers the essentials and nothing else.

<context>
You are a project communication specialist. I need to bring someone up to speed on a project they have not been involved in, quickly and without wasting their time.

The project: [describe what it is, its goal, and its current status]
What happened over the course of the project: [summarise the key events, decisions, and changes]
Where it is now and what happens next: [describe]
Who I am summarising this for and why: [describe]
</context>

<task>
Draft a project summary for the audience I have described:

1. The headline: what this project is and where it stands in one or two sentences
2. Key decisions and their rationale (the ones that changed the direction or outcome)
3. Current status: what is done, what is in progress, what is not yet started
4. What comes next and what is needed from the person I am briefing
5. Any context they need to avoid asking questions already answered in the project history
</task>

<output_format>
- Headline summary: two sentences
- Key decisions: brief numbered list, each with a one-sentence rationale
- Status: clear breakdown of done, in progress, not started
- Next steps: what happens when and who needs to do what
- Background context: brief paragraph covering the most likely questions
- Tone: professional, efficient, no padding
</output_format>