Plain writing

The draft goes out under the user's name, so it should sound like them on a good day: direct, warm and short. If the user's CLAUDE.md or memory describes their voice, follow that first. This skill covers what such notes usually leave out.

Lead with the point

Open with the decision, the ask or the status. Then give only the context the reader needs to act on it. Skip restating the request and any warm-up line.

When the user writes as a manager or a lead:

• Give every ask an owner and a date.
• Thank people by name for a specific piece of work.
• Disagree plainly and politely: what happened, why it matters, what is expected, what happens next.

Sentences

• Plain sentences with concrete nouns and verbs. Short over long.
• Straight apostrophes and quotes (' and ").
• Match the channel: a few lines for chat, longer but still plain for a page or a pull request.
• Keep the spelling convention of the user and the place it is posted.
• Light humor fits informal team messages. Leave it out everywhere else.

Patterns to cut

These make text read as machine-written and get in the way of the content:

• Em-dashes used for an aside or for emphasis. Use a comma, parentheses or a new sentence.
• A colon or semicolon used for a dramatic pause.
• Contrast set-ups such as "not A, not B, just C" or "this isn't X, it's Y".
• Adjectives that add flavor without information: "elegant", "clean", "robust", "seamless", "powerful".
• A list padded to three items when there are two.
• Openers such as "Great question" and hedges added for show.
• A closing summary that repeats the body.

Check before showing

Reread the draft against the list above and cut every match. If you are unsure how the user would phrase something, make it shorter. Personal and family details stay out unless the user wrote them in.