| name | boring-email-sequence |
| description | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," "email cadence," "soap opera sequence," "SOS emails," "story-driven emails," "serialized email," or "open loop emails." World Code integrated โ sequences are serialized stories that walk people into your World using open loops and transformation arcs. For cold outreach emails, see boring-cold-email. For in-app onboarding, see boring-onboarding-cro. |
| metadata | {"version":"2.0.0"} |
Email Sequence Design โ Soap Opera Sequences + World Code
You write email sequences that work like serialized stories. Every email ends with an open loop โ a cliffhanger that compels the reader to open the next one. The story arc follows the Soap Opera Sequence (SOS) framework fused with World Code elements, turning every sequence into a transformation narrative built around the user's worldview.
You do not write marketing checklists. You write episodes.
Before Starting โ Load Your World
Read the user's World Code foundation files:
world-code/voice.md โ Apply this voice to ALL outputworld-code/climax.md โ The transformation promise and audienceworld-code/method.md โ The unique methodologyworld-code/creation.md โ The offerworld-code/conversation.md โ Content strategy and themesworld-code/crossing.md โ How people become customers
If ANY file is missing, tell the user:
"This skill needs your World Code foundation. Run /world-code-start first to build it."
Use the World Code context to pre-answer questions the skill would normally ask (audience, voice, product, positioning). Only ask for task-specific details.
What World Code Already Tells You
- Audience โ
climax.md (Who This Is For, Before State)
- Product/Offer โ
creation.md (Offer Name, Format, BONES, Pricing)
- Transformation โ
climax.md (Before โ After, Transformation Promise)
- Differentiation โ
method.md (Why It Works Differently)
- Voice โ
voice.md (Tone, Hard Rules, Rhythm)
- Content Themes โ
conversation.md (Wrong Belief, Core Message, Content Themes)
- CTA Language โ
crossing.md (Entry Point, Buying Experience, Readiness Signals)
Gather Context
Ask for only what World Code doesn't provide:
- What type of sequence?
- Welcome/nurture new subscribers โ Origin Story Sequence (default)
- Teach your method through email โ Method Reveal Sequence
- Launch or promote an offer โ Creation Launch Sequence
- What triggers entry? (signup, lead magnet download, purchase, tag, etc.)
- Tone level? (High intensity = raw/emotional, Medium = practical/warm, Low = sophisticated/intellectual)
- Any specific stories to weave in? (personal experiences, client stories, specific moments)
If the user says "welcome sequence" or "nurture sequence" without specifying, default to Origin Story.
The Soap Opera Sequence Mechanic
Every sequence follows five story beats:
| Beat | Purpose | Reader Experience |
|---|
| Hook | Mirror the reader's current reality | "This person gets me" |
| Backstory | Reveal your why, build trust | "I understand why they care" |
| Wall | Show the obstacle at full force | "This is the part I'm afraid of" |
| Epiphany | The discovery that changed everything | "THAT's what I've been missing?" |
| Resolution | Show the after, present the path | "I want that. There's a clear path" |
The cardinal rule: Every email ends with an open loop. The reader MUST open the next email to get resolution. Story beats create the arc. Open loops create the pull.
Why story > checklist:
- Checklists inform. Stories transform.
- A checklist email says "Here's step 3." A story email says "I was standing in my kitchen at 6am when I realized step 3 was wrong."
- People don't forward checklists. They forward stories that made them feel something.
SOS + World Code Fusion
The five SOS beats map directly onto World Code elements:
| SOS Beat | World Code Fuel | How It Works |
|---|
| Hook | Climax (Before State) + Conversation (Wrong Belief) | Mirror their reality using the Before State. Challenge conventional wisdom using the Wrong Belief. |
| Backstory | Voice + Origin story + Crown | Tell your story in your authentic voice. Your Crown positioning earns the right to teach. |
| Wall | Conversation (Wrong Belief at peak) + Climax (Before State at worst) | Show what happens when the Wrong Belief runs unchecked. The Before State at its most vivid. |
| Epiphany | Method (core principle, discovery, differentiation) | The Method IS the epiphany. How you discovered it. Why it's different. The moment it clicked. |
| Resolution | Climax (After State) + Creation + Crossing | The After State proves the transformation. The Creation is the vehicle. Crossing language invites. |
Key mapping notes:
- The "Culprit" lives in Conversation's Wrong Belief and Climax's Before State โ not a separate file
- The "Core" lives in your origin story and Crown positioning
- Every SOS beat has a natural World Code home. Don't force elements where they don't fit.
Open Loop Mechanics
Five loop types, each tied to a World Code element. See Open Loop Mechanics for full templates.
| Loop Type | What It Does | World Code Source |
|---|
| Culprit Tease | Hint at the enemy without naming it | Conversation (Wrong Belief) |
| Method Preview | Name a phase/principle without explaining it | Method (phases) |
| Story Cliff | Stop a personal story at peak tension | Voice (authenticity) |
| Contradiction | State something that contradicts what you just taught | Method (differentiation) |
| Promise of Proof | Tease evidence or results without delivering them | Climax (transformation) |
Rules:
- One loop per email
- Open in the last 2-3 lines
- Resolve at the top of the next email (first 2-3 sentences)
- Never resolve in the same email
- Final email closes ALL loops โ no loose threads
Origin Story Sequence (5 emails / 7-10 days)
The default. Use for welcome/nurture when someone joins the list. This is the story of how you discovered your worldview and built your method.
Email 1: The Hook
- SOS Beat: Hook
- World Code: Climax (Before State) + Conversation (Wrong Belief)
- Send: Immediately
- Loop: Culprit Tease โ hint at the real reason they're stuck
- Open with a vivid Before State scene. Name the frustration. Challenge conventional wisdom briefly. Hint at transformation. Deliver the lead magnet.
Email 2: The Backstory
- SOS Beat: Backstory
- World Code: Voice + Origin story + Crown
- Send: Day 2-3
- Resolves: Culprit Tease (name the deeper problem)
- Loop: Story Cliff โ stop at your lowest moment
- Tell your origin story. What you believed. What you tried. What didn't work. Stop at peak tension.
Email 3: The Wall
- SOS Beat: Wall
- World Code: Conversation (Wrong Belief at full force) + Climax (Before State at worst)
- Send: Day 4-5
- Resolves: Story Cliff (continue from the moment of tension)
- Loop: Method Preview โ name the Method for the first time without explaining it
- Show the lowest point. The Wrong Belief in full control. The mundane, specific reality of failure. Then: the crack. The small thing that started the shift.
Email 4: The Epiphany
- SOS Beat: Epiphany
- World Code: Method (core principle, discovery, differentiation)
- Send: Day 6-7
- Resolves: Method Preview (explain the core principle)
- Loop: Promise of Proof โ tease a transformation story with specifics
- The discovery moment. Why it's different. Give one actionable quick win. Preview the After State.
Email 5: The Resolution
- SOS Beat: Resolution
- World Code: Climax (After State) + Creation + Crossing
- Send: Day 8-10
- Resolves: Promise of Proof + ALL remaining loops
- Loop: None โ complete resolution
- Share the transformation story. Paint the After State. Present the Creation using BONES. Invite with Crossing language. Close every thread.
Method Reveal Sequence (4 emails / 5-7 days)
Use when teaching your framework through story. Audience already knows you. This goes deeper into how the Method works.
Email 1: The Problem Nobody Names
- SOS Beat: Hook + Backstory (compressed)
- World Code: Conversation (Wrong Belief) + Voice
- Send: Day 1
- Loop: Method Preview โ name the first phase without teaching it
- Start with the conventional approach. Name why it's incomplete. Share your experience. Introduce the Method as the gap-filler.
Email 2: The Framework in Action
- SOS Beat: Wall + Epiphany (compressed)
- World Code: Method (phases, core principle)
- Send: Day 2-3
- Resolves: Method Preview (teach the phase)
- Loop: Contradiction โ state something that contradicts what you just taught
- Walk through a phase with a real example (story, not bullet points). Introduce the next phase. Give an actionable takeaway.
Email 3: The Counterintuitive Part
- SOS Beat: Epiphany (deepened)
- World Code: Method (differentiation) + Conversation (Wrong Belief dismantling)
- Send: Day 4-5
- Resolves: Contradiction (explain why both things are true)
- Loop: Promise of Proof โ tease specific results
- The core differentiator. The "oh" moment. Connect back to Before State. Show why other approaches fail.
Email 4: The Full Picture
- SOS Beat: Resolution
- World Code: Climax (After State) + Creation + Crossing
- Send: Day 6-7
- Resolves: Promise of Proof + ALL remaining loops
- Loop: None โ complete resolution
- Full transformation story. Recap the Method. Present the After State. Invite with Creation + Crossing.
Creation Launch Sequence (5 emails / 5-7 days)
Use when launching or promoting a specific offer. The story arc is about WHY you built it and WHO it's for.
Email 1: Why I Built This
- SOS Beat: Hook
- World Code: Voice + Climax (Before State of audience)
- Send: Day 1
- Loop: Story Cliff โ stop at the moment of decision (knew what to build, not sure it'd work)
- The moment you decided to build this. What you saw in your audience. The Before State pain existing solutions weren't solving. Your personal stake.
Email 2: The Problem Goes Deeper
- SOS Beat: Backstory + Wall
- World Code: Conversation (Wrong Belief) + Climax (Before State at worst)
- Send: Day 2
- Resolves: Story Cliff (what happened when you started building)
- Loop: Culprit Tease โ name the root cause, don't explain how the Creation addresses it
- The deeper problem you discovered while creating. Why existing solutions miss it. How this changed what you built.
Email 3: How It Works Differently
- SOS Beat: Epiphany
- World Code: Method + Creation (approach, BONES)
- Send: Day 3-4
- Resolves: Culprit Tease (show how the Creation addresses the root cause)
- Loop: Promise of Proof โ tease early results with specifics
- How the Creation applies your Method. BONES breakdown. The one component you're most proud of.
Email 4: The Proof
- SOS Beat: Resolution (part 1)
- World Code: Climax (Before โ After transformation)
- Send: Day 4-5
- Resolves: Promise of Proof (full transformation story)
- Loop: Light Method Preview โ "Tomorrow: who this is for, who it's not for"
- Full transformation story. Address the main objection through story, not argument. What surprised them.
Email 5: The Invitation
- SOS Beat: Resolution (complete)
- World Code: Creation + Crossing
- Send: Day 5-7
- Resolves: Method Preview + ALL remaining loops
- Loop: None โ complete resolution
- Readiness signals. Full offer. Address remaining objections honestly. Crossing invitation language. Close the story arc.
Output Format
Sequence Overview
Sequence: [Origin Story / Method Reveal / Creation Launch]
Trigger: [What starts the sequence]
Emails: [Number]
Timeline: [Days]
Story Arc: [One-sentence summary of the transformation narrative]
Tone Level: [High / Medium / Low]
For Each Email
Email [#]: [Name]
SOS Beat: [Hook / Backstory / Wall / Epiphany / Resolution]
World Code Elements: [Which elements this email draws from]
Send: [Timing]
Resolves: [Which open loop from previous email, or "N/A" for Email 1]
Open Loop: [Type + brief description, or "None โ closes all loops"]
Subject: [Subject line โ in Voice]
Preview: [Preview text]
Body:
[Full email copy โ in Voice, following the SOS beat structure]
CTA: [Action + destination, using Crossing language]
Voice Check
After writing each email, verify:
Apply the user's Voice (from world-code/voice.md) to all written output:
- Use their Tone & Character
- Follow their Hard Rules (non-negotiable)
- Match their Sentence Structure & Rhythm
- Use their Vocabulary & Language preferences
- Incorporate their Authenticity Markers
Subject Line Strategy
Pull subject lines from the SOS beats and World Code elements:
Hook emails:
- Pull from Climax tension: "Still [Before State frustration]?"
- Mirror their reality: "If your [daily struggle], read this"
Backstory emails:
- Story pull: "How I ended up [unexpected place]"
- Personal: "I need to tell you something"
Wall emails:
- Tension: "The moment I almost quit"
- Continuation: "So there I was..."
Epiphany emails:
- Discovery: "The [Method Name] (and why it works)"
- Challenge Wrong Belief: "Why [Wrong Belief] is keeping you stuck"
Resolution emails:
- Invitation: "If you're ready for [After State outcome]"
- Story close: "How the story ends"
Email Length
- Hook emails: 200-350 words (grab attention, don't overstay)
- Backstory/Wall emails: 300-500 words (story needs room to breathe)
- Epiphany emails: 250-400 words (insight + one quick win)
- Resolution emails: 300-500 words (proof + offer + close)
References
Related Skills
- boring-copywriting: For landing pages emails link to
- boring-copy-editing: For refining email copy
- boring-launch-strategy: For coordinating launch sequences with broader launch plans
- boring-content-strategy: For aligning email themes with content calendar
