# Messages, replies and specs

Detail for the Two registers section of `gt-voice`. These are the shapes
Kevin set for work messages he sends or has an agent draft: Slack updates,
replies to the team, specs for a teammate and replies to an outside partner.
The hard rules of the skill hold in all of them.

## Slack about work

- A few lowercase sentences with the links and what each one is. No em
  dashes and no headers (2026-08-19: "combine this in a brief slack message
  ... no upper case no emdash").
- End-of-day recaps and PR slates follow `gt-reporting`.

## A team reply in Kevin's voice

The order Kevin used on 2026-07-21:

1. the diagnosis in one line;
2. the fix as two bullets;
3. why the fix is cheap;
4. the edge cases, with a light recommendation;
5. "thoughts?"

## A spec or handoff for a teammate

A paragraph in Kevin's voice, followed by numbered action items with
concrete examples (2026-09-02, 2026-09-03).

## A reply to an outside partner

For the brand agency, the video vendor or another partner (2026-09-24):

- Thank them at the start and at the end.
- Credit their reasoning before giving GT's.
- State the decision plainly.
- Name the constraints that decided it, and the ideas kept from their other
  options.
- Invite them to raise risks now.

Partner replies are friendly and still technical. A list of links stands in
for attachments where it can (2026-09-05). A brief for the video vendor
follows `gt-films` (Short media).

## Sources

- Kevin's messages: the team reply (2026-07-21), the brief Slack message
  (2026-08-19), the teammate specs (2026-09-02, 2026-09-03), the partner
  replies (2026-09-05, 2026-09-24).
- Kevin's wiki: `skills/personal/slack-voice/SKILL.md` (Slack drafts in
  general).