Skills / Departments / Marketing / Skills / Copywriting / Rmbc Email Sequence
All skills

/ skill

rmbc-email-sequence

Departments/Marketing/Skills/copywriting/rmbc-email-sequence.md

Generate a 7-14 day email sequence - welcome / nurture / promo / re-engagement based on funnel position.

Open as raw file

Run this skill

Heads up — this skill doesn’t have a structured form yet, so type the full prompt with all decisions baked in (the subprocess can’t answer follow-up questions). Edit me if needed.

Runs with bypassPermissions — local dev only.

rmbc-email-sequence

RMBC Stage 4 deliverable. Email Sequence (7-14 day).

Use case

Post-opt-in nurture, post-purchase customer journey (B->C+), abandoned-cart re-engagement.

Pre-flight

  1. brief_path exists and Brief 2.0 has all 25 sections filled (status: reviewed or approved).
  2. Read brand context: Brands/{brand_slug}/BrandContext.md, voice-profile.md, compliance.md.
  3. Read the canonical Claude Project system prompt at References/rmbc/claude-projects/08-email-sequences.md - that's the load-bearing prompt. Follow it.
  4. Read PLAYBOOK.md sections 5 (VSL Structure) / 7 (Asset Matrix) for length / shape conventions.

Procedure

Follow the procedure in claude-projects/08-email-sequences.md exactly. The skill blueprint here is the wrapper - that file is the substantive prompt.

Asset-specific rules

  • Each email = subject line + preview text + body + CTA.
  • Subject lines: 5+ variants per email for A/B testing.
  • Day cadence: most-aware emails first 3 days, education middle 4-7, urgency-driven final 3.
  • Match brand voice exactly - emails are the most personal channel.

Output

Path: Brands/{brand_slug}/Marketing/drafts/{date}-email-{sequence_kind}-{slug}.md

Frontmatter:

---
type: copy-draft
brand: {brand_slug}
asset_type: email-sequence
brief_ref: "<a class="wikilink wikilink-broken" href="#">{brief_path}</a>"
status: draft
created: YYYY-MM-DD
---

Body: outline (if asset >= medium length, request approval first) -> full draft -> editing notes (voice fit, compliance flags, specificity gaps, alternates).

Log entry

Append to Wiki/Log.md via the standard format. Include the asset type and brief reference.

Hard rules

  • No copy without an approved Brief. Period.
  • Never fabricate. If the Brief is missing data, surface the gap.
  • Cite library evidence in the editing notes when libraries were queried.

Failure modes

  • Brief sections missing or marked TBD - abort, route back to rmbc-brief.
  • Brand voice-profile / compliance still placeholder - surface as blocker.
  • Output truncated - ask user "continue"; never compress.