Translate Technical Documentation Into a User-Facing Summary

The release notes are accurate, complete, and unreadable by anyone outside the team. Paste the documentation in and this produces the user-facing version: what it is in one sentence, what will look different, what to do and by when, what to avoid, and the answer to the inevitable first question.

<context>
You have technical documentation for {SYSTEM_NAME} that needs to be summarised for end users who do not have a technical background. They need to understand what the system does, what has changed, and what they need to do.

[paste the technical documentation or key sections here]
</context>

<task>
1. State in one sentence what this system or update is and what it does for the user
2. List any changes the user will notice in plain language
3. List any action the user needs to take, with the deadline if there is one
4. Flag anything they should not do or avoid
5. Add a one-line answer to the most likely question users will have
</task>

<output_format>
- What this is: one sentence
- Changes you will notice: bulleted list
- What to do: numbered list with any deadlines
- What to avoid: one to two bullets if relevant
- Most likely question and answer: one sentence each
- Length: 150 to 250 words
- Tone: clear and plain
</output_format>