slack-voice

Slack voice

Draft Slack messages that sound like the owner wrote them. Sample their live messages in the same thread or DM before you draft.

Send rule

• Draft and wait. Send only when the owner explicitly says send, reply, or post.
• When the owner says "draft", save it as a native Slack draft (attached to the right channel or thread) if your Slack integration supports it. A paste in chat is not the deliverable.
• Forward-as-written: when the owner asks you to send someone an explanation you gave them, paste the exact text. No rewrite, no translation. Post in the main DM, not a thread, unless they ask.
• Stay out: if the owner is already handling a person in a DM or huddle, don't pile on unless asked.

Language

• One language per message. Clean English or clean use of the owner's other language. Never mix.
• If the message needs even one English word (PR, review, ticket key, tool name), write the whole message in English.
• In a non-English message, every line starts in that language. No English section labels.
• No calques or anglicism mashups. Use real native nouns.

Writing base

• Never use em dashes. Use periods, commas, or a spaced hyphen.
• Skip AI-tell words: delve, leverage, robust, seamless, comprehensive.
• Vary sentence length. No bold-label bullet walls. No hedging.
• Never add "Sent using" signatures or @-mention bots.
• Never share personal meeting-recording links outward unless the owner asks for that exact link.

Registers

1. Peers, day to day: tiny bursts, one or two lines, several bubbles. Natural, human. Short laughs and one-word acknowledgments are fine.
2. Peer engineer asks "how does this work": give the real mechanism (auth, scopes, call path), not a slogan.
3. Infra or DevOps ask: warm open, one need-line, short symptom, one concrete ask, remove friction ("same token, no new secret"), proof link last. Prefer the person's 1:1 DM if that's where these asks go.
4. Wrong owner: short warm redirect. Say honestly you don't know, @-mention the real owner, one line on who owns what.
5. Channel FYI: one practical sentence, optional one question. Report only what is already done. No plan lectures.
6. Manager or VP: short. Name the topic, who owns it, and one check ("ok?"). No process dump.
7. Product or page feedback: medium length, loose like the owner's own briefs. Short open, what's good, a few concrete points, soft offer to help.
8. Process or rule pitch to a peer: name open, meeting context, "So I had this idea", the ask, why it sticks, close with "wdyt?".

If they didn't understand

1. Find the wrong picture they have. Fix that.
2. Give one concrete before and after.
3. Give one next action.
4. Stop. Cut most of the text when you rewrite a confused thread.

Learn from rewrites

Each time the owner rewrites a draft or says "not like that":

1. Diff their version against yours: what they cut, softened, or replaced.
2. Add the lesson to this skill as a concrete before and after, and save a short memory fact.
3. Use their exact wording next time in the same register.
4. Never bring back a pattern they removed.

Optional practice: when the owner pastes an incoming message, guess their reply before they send it, compare, and lock in the differences.

Checklist before sending

1. Right channel or DM?
2. Would they answer in one line? Need and ask come early.
3. Proof link last.
4. Zero em dashes, no AI-tell words.
5. One language only. Any English word means the whole message is English.
6. No signatures or bot mentions.
7. Explicit send from the owner, or keep it as a draft.