Use case: Professional & Workplace Communication
Instruction type: Conditional
Prompt style: Direct prompting

Prompt:
I need a Slack message drafted for work to be sent to my team. They need to know that there was a sudden change in project deadlines. The new deadline is one week sooner. The design team messed up the ordering, and my team needs to know but I don’t want it to sound like I’m blaming them. Acknowledge that this will require extra effort/work. I want the message to be professional, yet casual enough for Slack (emojis). Don’t write anything that will cause panic. Avoid apologizing for the situation. If the message goes over 150 words, use bullet points to highlight the main points, but the bullet points should not repeat any content already in the other paragraphs. Include an announcement regarding a quick team check-in tomorrow at 3PM ET, but note that it is not mandatory. The meeting will be held in my personal zoom room. Offer my support via Slack or email. End the message with a reassuring statement but don’t make it one of those generic “we got this” sort of deals.

Evaluation criteria:
The response should be presented as a single Slack message to a work team. For example, use concise, conversational paragraphs in a style that would feel natural when quickly skimmed in Slack.
The response should state that the project deadline has been moved up by one week.
The response should attribute the deadline change to an ordering issue from the design team.
The response should not assign blame for the deadline change to the design team. For example, it could use neutral phrasing like "due to a realignment of design deliverables" or "a change in the project sequence".
The response should acknowledge that the accelerated deadline will require extra effort or work from the team. For example, it could include a short comment that highlights the impact on workload or schedule.
The response should have a professional yet casual tone appropriate for Slack. For example, the language should be clear and direct, but can be conversational.
The response should include at least one emoji.
The response should not use language that is likely to cause panic. For example, it should avoid alarmist words such as "emergency" or "crisis".
The response should not contain an apology for the deadline change. For example, it should not include "I'm sorry" or "I apologize".
The response should contain a bulleted list if over 150 words.
The response should not use bullet points to repeat information already stated in the main paragraphs. For example, it should not mention things like the deadline date, check-in meeting, or the reason for the deadline change in a bullet point if that information has been touched on elsewhere.
The response should announce a team check-in meeting scheduled for "tomorrow".
The response should specify that the meeting time is 3 PM ET.
The response should state that attendance at the meeting is not mandatory.
The response should specify that the meeting will be held in the sender's personal Zoom room.
The response should offer the sender's support via Slack and email.
The response should end with a reassuring statement. For example, it could express confidence in the team's ability to handle the new timeline.
The response should ensure the final reassuring statement is not a generic cliché. For example, it should avoid phrases like "we got this," "let's crush this," or "teamwork makes the dream work."
The response should reference the team meeting as quick. For example, it could use the word "quick" or "brief" when announcing the check-in and/or meeting.