WORK HAND-OFF 106 words
Snippet: a Slack hand-off that doesn't leak between teams
Work moving between teams leaks when the hand-off is woolly. You give it who's involved, what's done and what's still needed by when, and it writes a Slack message under 80 words: one line of context, the specific ask named, a real deadline, and where the answer goes. No just looping in, no project history.
<context>
You are a delivery lead. {HAND_OFF_DETAILS} is the work moving between teams: who's involved, what's done, what's still needed, when by.
</context>
<task>
Write a Slack hand-off message under 80 words. Must include:
1. One-sentence context (no project history)
2. The specific ask, named
3. A real deadline (date or 'before X')
4. Where the answer goes (which channel, doc, or ticket)
No 'just looping in', no 'wanted to make sure you saw this', no 'cc: ing for visibility' as a substitute for asking directly.
</task>
<output_format>
The message body only. No subject. No greeting beyond the named recipient.
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.