Composing a Routine Email¶
Source: hooks/ways/ea/email/drafting/composition/composition.md
Frontmatter
| Field | Value |
|---|---|
description |
keeping a routine email to a few plain lines with one ask and the next step, written as a peer, raising a slipped deadline or other sensitive matter with the narrowest audience and without blaming anyone, and keeping everyone who was cc'd on it |
vocabulary |
few lines plain mail client tables markdown separate document peer accusing blaming sensitive narrowest audience manager cc cc'd copied mailbox superseded recurring template pushback scheduled |
refire |
0.15 |
scope |
agent, subagent |
Match how the user writes to this recipient in this context. Real sent mail outranks any style guide. AI tics found in AI-assisted documents are not the user's style. Keep the email register separate from chat.
Shape¶
- When sent mail gives little to go on, routine mail runs 2 to 5 sentences with one ask and the next step. Then it stops.
- Write for an ordinary mail client. Use simple bullets at most. Do not use tables, ASCII art, or heavy markdown.
- Use the recipient's own wording and questions, and include any action the recipient must take. Do not repeat back data they already stated.
- When there is a lot of detail, offer to move it into a separate document.
- To explain a fix, say what was wrong and what changed, one sentence each, such as "Renamed the field to match the API."
- A recap email that serves as a record may use numbered bold headings.
Tone¶
- Keep it short, direct, and warm without gushing.
- Write as a peer focused on alignment, not as a boss. Apologize lightly for a delay where it fits.
- Stay matter-of-fact, never accusatory. Raise a sensitive issue with the narrowest audience first, such as the manager only, and still put the key facts in writing.
- Answer pushback with the facts. Do not call it speculation or unsubstantiated.
- Add no commitments or polish the user did not state. Keep every thread participant on the reply.
Handing over the draft¶
- Create the draft in the correct account's mailbox. Tell the user where it lives.
- Attach nothing unless asked. When files need to go out, put them in one folder the user can attach by hand.
- For recurring emails such as weekly updates, mirror the last instance's wording, addressees, and CCs. When the user changes the standard, update the template or skill that produces it, and name the update in your final message.
- Do not resend a draft that the user's sent mail has already superseded.
- If the user sends an email themselves and a chat follow-up depends on it, wait for their confirmation before posting the follow-up.
- Schedule a send only when the user has authorised it, and confirm the exact time and timezone first.
- Before presenting a draft, check it against any style rules the user has set.
See Also¶
- email/drafting(ea) — parent: style calibration from sent mail, threading, the drafts-only rule
- accounts(ea) — which mailbox a draft belongs in