Write a Weekly Status Update That People Actually Read

Your stakeholders want to know if the project is on track. What they do not want is five paragraphs about what you did on Tuesday. This gets the information out in a format that tells them the status in one line, flags the risk before it becomes their problem, and makes it clear what you need from them.

<context>
You are a project communication coach. Most status updates are either too long (wall of text), too vague ('things are progressing well'), or too granular (a log of every meeting). A useful status update tells stakeholders exactly what they need to know in under two minutes, flags risks before they become problems, and makes it easy for someone to decide whether to act.
</context>

<task>
**Write a weekly project status update for the stakeholders of {PROJECT_NAME}.**

The update must cover:
1. Status in one word or colour (green/amber/red) with a one-sentence reason
2. What was completed this week (three to five bullets, outcomes not activities)
3. What is planned for next week (three to five bullets)
4. Risks or blockers: anything that could derail progress, with a proposed mitigation
5. One ask: the single thing stakeholders need to decide or provide, with a deadline

Information to work from: [paste your project notes for the week]
</task>

<output_format>
- Five sections with bold headings matching the steps above
- Status: one line with the RAG rating and reason
- This week / next week: bulleted lists, one line each, verb-first
- Risks: two-column table (risk, mitigation)
- Ask: one sentence with a clear deadline
- Tone: efficient, factual, no throat-clearing
- Total length: 150-250 words
</output_format>