The prompt
Score 10 of 10, Excellent
Use it when Something is changing for your team, such as a reorg, new priorities or a new process, and you need to explain it clearly before rumors do it for you.
- {{team}}
- {{channel}}
- {{change_notes}}
- {{not_shareable}}
Full prompt and why it works
Prompt
# Role You help managers announce changes to their teams in plain, honest language. # Goal Draft a message for my team, {{team}}, announcing the change described in the Context section, to be sent by {{channel}}. People should come away knowing what is changing, what is not, why, what it means for them, and what happens next. # Success criteria - The change is stated in the first two sentences. - The reason is the real one from my notes, stated plainly, without spin. - Each person can find the answer to "what does this mean for me?" for their situation. - Likely questions are answered, or the message says when they will be. # Constraints - Use only the facts in my notes. Do not invent dates, numbers, reasons or reassurances. In particular, do not promise that jobs, pay, roles or reporting lines are unaffected unless the notes say so. - Keep a direct, human tone: short sentences, "we" and "you", and no corporate euphemisms such as "rightsizing" or "exciting journey". - Leave out anything listed as not yet shareable. # Output 1. The message: a subject line and 200 to 350 words, with these short sections: What's changing, What's not changing, Why, What it means for you, What happens next. 2. A short FAQ: 4 to 6 likely questions with answers from the notes. Where the notes do not answer a question, write "We don't know yet; we'll update you by [date to confirm]". 3. A list of anything in my notes that looks sensitive or legally significant (for example changes to roles, pay or locations), for me to check with HR or legal before sending. # Stop rules If my notes are unclear about whether something is decided or still under discussion, treat it as undecided and flag it in part 3. # Context <change_notes> {{change_notes}} </change_notes> <not_yet_shareable> {{not_shareable}} </not_yet_shareable>
Variables
- {{team}}
- Who receives it, for example "the customer operations team".
- {{channel}}
- For example email, a team chat post, or a script for a team meeting.
- {{change_notes}}
- What is changing and when, why, who is affected and how, and what is decided versus still open.
- {{not_shareable}}
- Anything that must not be shared yet. Write "none" if everything can be shared.
Why it works
- What to avoid. It forbids reassurances the notes do not support, such as promising jobs are unaffected, which do the most damage if they turn out to be wrong.
- Format. Fixed sections, including What's not changing, answer the questions people actually ask after a change is announced.
- If unsure. Anything undecided or legally sensitive goes on a list for you to check with HR or legal before sending.