name	consulting-email-atomizer
description	Fan one source insight into several scheduled, segment-routed email touches (trend-jack, proof, insight, build-in-public, 1:1 nudge) staged as drafts, never one-offs. Use after a call/extraction, on "turn this into emails", "atomize for email", "what should I send the list", or when a notable industry event lands. Powers the top-of-funnel email engine.

Consulting Email Atomizer

Turn one source (a signals/ entry, a fresh call, or an industry event) into several email touches. Second consumer of the signal reservoir (LinkedIn is the first). Full design: docs/plans/2026-06-19-email-engine-design.md · templates: library/email-templates/ (06-11) · staging + frontmatter + routing: email/AGENTS.md. Voice + gate (always): write in consulting-copy-writer voice, then run every draft through the consulting-outbound-email skill (read context, route to the right person, reader-POV check, names verified) before staging.

Steps

Take one source. Prefer an existing signals/ entry. If it is a raw call, run consulting-content-extraction first so the signal exists. Record its path. It becomes source:. No source, no email.
Atomize. Decide which of the 6 formats this source can honestly yield (most yield 2-4, not all 6). A weak fit is a skip. Don't pad.
Route. For each chosen format, apply the default routing (email/AGENTS.md): trend-jack → cold/warm/targets · proof → everyone · insight → warm/targets/customers · build-in-public → customers/warm · nudge → one named person · newsletter → whole list.
Resolve segments live. Query Attio (ATTIO_API_KEY) for current membership of each target segment. Reconcile-on-touch, never a copied list. For a 1:1 nudge, pick the one named contact.
Draft each touch. Fill the matching library/email-templates/ skeleton in Sid's voice. Always apply consulting-copy-writer (the voice) and the consulting-outbound-email gate (names verified against real context). Borrow consulting-content-drafter's AIDA and "you over I". Ground every claim in the source. No invented numbers, streams, or chart positions.
Stage. Write each to email/outbox/<send_date>-<format>-<segment>.md with the instance frontmatter (format · source · audience/recipient · send_date · status: draft · channel: gmail).
Report the fan-out (1 source into N drafts) with proposed send_dates spread across the week. Never send. Offer to stage Gmail drafts via integrations/gmail/_work/create_draft.py only on confirmation.

Output: N staged email drafts in email/outbox/, each tracing to one source. Source: Ch. 3/5 (atomization plus the multi-format test) plus docs/plans/2026-06-19-email-engine-design.md.

Consulting Email Atomizer

Steps

Take one source. Prefer an existing signals/ entry. If it is a raw call, run consulting-content-extraction first so the signal exists. Record its path. It becomes source:. No source, no email.

Atomize. Decide which of the 6 formats this source can honestly yield (most yield 2-4, not all 6). A weak fit is a skip. Don't pad.

Route. For each chosen format, apply the default routing (email/AGENTS.md): trend-jack → cold/warm/targets · proof → everyone · insight → warm/targets/customers · build-in-public → customers/warm · nudge → one named person · newsletter → whole list.

Resolve segments live. Query Attio (ATTIO_API_KEY) for current membership of each target segment. Reconcile-on-touch, never a copied list. For a 1:1 nudge, pick the one named contact.

Draft each touch. Fill the matching library/email-templates/ skeleton in Sid's voice. Always apply consulting-copy-writer (the voice) and the consulting-outbound-email gate (names verified against real context). Borrow consulting-content-drafter's AIDA and "you over I". Ground every claim in the source. No invented numbers, streams, or chart positions.

Stage. Write each to email/outbox/<send_date>-<format>-<segment>.md with the instance frontmatter (format · source · audience/recipient · send_date · status: draft · channel: gmail).

Report the fan-out (1 source into N drafts) with proposed send_dates spread across the week. Never send. Offer to stage Gmail drafts via integrations/gmail/_work/create_draft.py only on confirmation.

Output: N staged email drafts in email/outbox/, each tracing to one source. Source: Ch. 3/5 (atomization plus the multi-format test) plus docs/plans/2026-06-19-email-engine-design.md.

consulting-email-atomizer