[needs source]

memory/email/email-creative-builder/

• Reads: the offer/topic, destination, email mode, audience/lifecycle stage, existing copy,

  memory/projections/narrative.json

  ,

  memory/projections/claims.json

  , and the live consent/suppression state required by the selected flow.
• Writes: a user-facing email creative and, with permission, a WARM artifact; unresolved claims become authorized proposal events, never direct ledger edits.
• Done when: subject/preheader fit declared render limits, the body has one primary CTA, plain text exists, claims/disclosures are accepted and context-valid or visibly blocked, destination message-match holds, and the Narrative/claims dependency tuple is present.
• Primary next skill: send-experiment-designer — design the A/B / send-time test across the subject variants; or email-quality-auditor to score the unit and run the D1 claim veto.

Emit the standard shape from skill-contract.md §Handoff Summary Format, including the Narrative/claims dependency tuple.

narrative_canon_id

narrative_canon_version

claims_projection_offset

dependency_status: verified | approved-fallback | blocked

1. Confirm inputs — offer/topic, destination URL, mode (promo / cold / newsletter), persona or lifecycle-stage, brand voice, and goal. If the destination URL is missing, you cannot enforce message-match — see the Decision Gate / NEEDS_INPUT path.
2. Read the destination — extract the page's headline, primary value prop, the concrete offer/claim, and the CTA. This is the message-match anchor; the subject, body, and CTA must echo it. A user who clicks the email must land on a page that delivers what the email promised (the SEND-D message-match lever).
3. Set the mode — apply the pattern set for the confirmed mode from references/email-creative-modes.md:
   • B2C promo/lifecycle — offer-led, urgency/social-proof used honestly, one dominant CTA.
   • B2B cold-outbound — personalization on a named signal, relevance-first, low-pressure ask; no fabricated familiarity.
   • Newsletter — value-led editorial, sponsor/monetization slot kept distinct from editorial, one primary action.
4. Draft subject-line variants — 3-5 distinct subjects (curiosity, benefit, offer, personalization, question) plus one matched preheader, each within inbox render limits from references/subject-line-specs.md. These variants are the raw material send-experiment-designer tests — label them so they carry into the test.
5. Write the body + one CTA — structured, scannable body copy with a single primary CTA that lands on the destination URL. One email, one job. Secondary links stay subordinate.
6. Resolve L1 truth — read accepted Narrative canon and claims projection at named offsets. Use only wording approved for this audience, jurisdiction, offer window, and email mode; a registry row outside its scope does not authorize reuse.
7. Propose unresolved claims — keep

   [needs source]

   inline and submit an authorized, idempotent

   operation: propose

   event through

   registry-events.py

   . Flag, do not silently delete or invent substantiation; a material unresolved claim blocks ready-to-send status.
8. Enforce message-match — annotate each claim-bearing line with the destination claim it echoes. Drop any line that promises something the page does not deliver (a SEND-D message-match failure and a D1 risk the auditor will veto).
9. Produce the plain-text alternate — a readable text/plain version of the same message (deliverability + accessibility hygiene). No image-only email.
10. De-slop — run humanizer-slop.md to strip AI tells before handoff.

[needs source]

• Stop and ask — destination URL missing and not inferable from context (message-match cannot be enforced; return NEEDS_INPUT naming the missing URL); mode ambiguous between promo and cold-outbound when the copy strategy diverges sharply. Present numbered options with their outcomes.
• Continue silently — brand voice unspecified (infer a neutral professional tone and note the assumption); no past-campaign export (proceed with general subject-line craft, mark angle-fit Estimated); optional persona detail missing (use the stated audience, flag the gap). Do not stop for which 3 of 5 subject angles to draft — pick the highest-fit set for the mode and note it.

• Email Creative Modes — the promo / cold-outbound / newsletter pattern sets and the message-match map template
• Subject Line Specs — inbox render limits, preheader length, and variant-labeling for hand-off to the test
• SEND Benchmark — the framework; this skill produces the E/D unit that email-quality-auditor scores and D1 vetoes
• Humanizer Slop Check — pre-handoff pass that strips AI-slop phrasing

• Primary: send-experiment-designer — design the A/B / send-time test across the subject-line variants once the creative is ready.
• To score + run the claim veto: email-quality-auditor — computes the profile-weighted EQS and enforces D1 (claim integrity) plus the other vetoes. This skill does neither.
• If claims carry

  [needs source]

  flags: offer-claims-registry — register the claims with evidence provenance and approved wording, then swap the resolved wording back into the flagged lines.
• If the destination URL is weak or missing (NEEDS_INPUT): landing-optimizer — fix the post-click page so message-match is achievable, then return here.
• Global visited-set / max-depth termination contract from skill-contract.md applies; if the recommended next skill was already run this session, or routing is ambiguous, stop and report options instead of auto-following. Stop when the creative set is test- or auditor-ready.