@growthub/cli 0.14.4 → 0.14.6

package/assets/worker-kits/growthub-email-marketing-v1/templates/hooks-library/subject-line-patterns.csv

@@ -1,73 +0,0 @@
-Type,Campaign Type,Pillar,Example,Structure
-curiosity,nurture,automation,"The thing most performance teams miss about scaling creative","The thing most [PERSONA_ROLE]s miss about [TOPIC]"
-curiosity,nurture,automation,"Your creative bottleneck isn't where you think it is","Your [PAIN_POINT] isn't where you think it is"
-curiosity,nurture,growth-system,"Your growth problem isn't actually a growth problem","Your [PAIN_POINT] problem isn't actually a [PAIN_POINT] problem"
-curiosity,nurture,education,"Why most testing programs don't compound (and how to fix it)","Why most [COMMON_APPROACH]s don't [DESIRED_OUTCOME] (and how to fix it)"
-curiosity,nurture,education,"The framework behind every high-win-rate creative program","The framework behind every [DESIRED_OUTCOME] program"
-curiosity,cold,automation,"The bottleneck most performance directors don't see coming","The bottleneck most [PERSONA_ROLE]s don't see coming"
-curiosity,cold,automation,"Why your creative cycle is slower than it looks","Why your [PROCESS_NAME] is [PROBLEM] than it looks"
-curiosity,cold,education,"Nobody talks about this part of the testing process","Nobody talks about this part of the [PROCESS]"
-curiosity,cold,pipeline,"Why your pipeline isn't dead — it's just quiet","Why your [ASSET] isn't [NEGATIVE_STATE] — it's just [DIFFERENT_STATE]"
-curiosity,cold,education,"The difference between brands scaling and brands plateauing","The difference between [SUCCESS_STATE] and [STUCK_STATE]"
-curiosity,re-engagement,pipeline,"Something we should have sent sooner","Something we should have sent sooner"
-curiosity,re-engagement,automation,"What's changed since we last talked","What's changed since we last talked"
-curiosity,re-engagement,results,"One thing that might change how you see this","One thing that might change how you see [TOPIC]"
-curiosity,follow-up,growth-system,"The thing you mentioned that stuck with me","The thing you mentioned that stuck with me"
-curiosity,follow-up,automation,"One more thing from our call worth considering","One more thing from [CONTEXT] worth considering"
-social-proof,nurture,results,"How one agency went from creative chaos to a systemized growth machine","How [PERSONA_TYPE] went from [PAIN_STATE] to [DESIRED_OUTCOME]"
-social-proof,nurture,results,"From 100K to 500K in ad spend — what actually changed","From [METRIC_BEFORE] to [METRIC_AFTER] — what actually changed"
-social-proof,nurture,automation,"5x more creative tests per month — the system behind it","[RESULT] — the system behind it"
-social-proof,nurture,results,"What brands removing the creative bottleneck have in common","What [PERSONA_TYPE]s achieving [OUTCOME] have in common"
-social-proof,nurture,pipeline,"27% of dead leads replied to this sequence — here's why","[PROOF_NUMBER] of [AUDIENCE_TYPE] [RESULT] — here's why"
-social-proof,cold,results,"What top CGOs are doing that most brands aren't","What top [PERSONA_ROLE]s are doing that most [COMPETITOR_TYPE]s aren't"
-social-proof,cold,automation,"The agencies scaling fastest have this in common","The [PERSONA_TYPE]s [RESULT] have this in common"
-social-proof,cold,results,"How [brand type] tested 3x more concepts without hiring","How [PERSONA_TYPE] [RESULT] without [COST_OR_EFFORT]"
-social-proof,re-engagement,results,"Here's what happened when we applied this to a list like yours","Here's what happened when we applied this to [AUDIENCE_TYPE]"
-social-proof,re-engagement,pipeline,"11 booked calls from a list everyone wrote off","[SPECIFIC_RESULT] from [AUDIENCE_TYPE] everyone wrote off"
-social-proof,follow-up,results,"The case study I mentioned — worth reading before our next call","The [PROOF_ASSET] I mentioned — worth [ACTION] before [NEXT_STEP]"
-urgency,nurture,automation,"Every week without a testing system is a week your competition is ahead","Every [TIME_UNIT] without [SOLUTION] is a [TIME_UNIT] [COST_OF_DELAY]"
-urgency,nurture,pipeline,"The pipeline you have right now won't look this way in 30 days","The [ASSET] you have right now won't [STATE] in [TIMEFRAME]"
-urgency,nurture,automation,"While you're waiting on creative production, your ad account is sitting still","While you're [CURRENT_STATE], [WHAT_IS_HAPPENING_WITHOUT_YOU]"
-urgency,promotional,pipeline,"This closes Friday — last chance to lock in [OFFER]","This closes [DATE] — last chance to [ACTION]"
-urgency,promotional,results,"[N] spots left for [OFFER]","[N] spots left for [OFFER]"
-urgency,promotional,automation,"The window for [OFFER] closes [DATE]","The window for [OFFER] closes [DATE]"
-urgency,re-engagement,pipeline,"The deals that come back don't wait forever","The [ASSET] that [RESULT] don't wait forever"
-urgency,re-engagement,pipeline,"Last email on this — then I'll leave you alone","Last email on this — then I'll leave you alone"
-urgency,cold,pipeline,"Last email from me on this, [First Name]","Last email from me on this, [FIRST_NAME]"
-urgency,follow-up,pipeline,"Quick question before I go quiet","Quick question before I [ACTION]"
-urgency,follow-up,pipeline,"Still [desired outcome]? Here's the thing.","Still [DESIRED_OUTCOME]? Here's the thing."
-personal,cold,automation,"[First Name] — quick question about your creative pipeline","[FIRST_NAME] — quick question about your [PROCESS_NAME]"
-personal,cold,growth-system,"For CGOs hitting the creative ceiling on Meta spend","For [PERSONA_ROLE]s hitting [PAIN_POINT]"
-personal,cold,pipeline,"[First Name], you know this feeling","[FIRST_NAME], you know this feeling"
-personal,cold,education,"[First Name] — something I think you'll find useful","[FIRST_NAME] — something I think you'll find useful"
-personal,re-engagement,pipeline,"Hey [First Name] — checking in","Hey [FIRST_NAME] — checking in"
-personal,re-engagement,pipeline,"[First Name] — still relevant?","[FIRST_NAME] — still relevant?"
-personal,re-engagement,pipeline,"[First Name], something changed","[FIRST_NAME], something changed"
-personal,follow-up,results,"Following up from our call, [First Name]","Following up from [CONTEXT], [FIRST_NAME]"
-personal,follow-up,growth-system,"[First Name] — picking up where we left off","[FIRST_NAME] — picking up where we left off"
-personal,nurture,growth-system,"This one's for [PERSONA_ROLE]s like you","This one's for [PERSONA_ROLE]s like you"
-personal,cold,automation,"[First Name], this might land differently now","[FIRST_NAME], this might land differently now"
-direct,nurture,automation,"Scale ad spend without increasing creative costs","Scale [OUTCOME] without [COST]"
-direct,nurture,growth-system,"The operating system for growth — not a tool","The [CATEGORY] for [DESIRED_OUTCOME] — not [WRONG_CATEGORY]"
-direct,nurture,results,"More winning ads, faster, without more headcount","More [OUTCOME_1], [SPEED], without [COST]"
-direct,promotional,pipeline,"Your growth call is ready to book","Your [CTA_OUTCOME] is ready to [ACTION]"
-direct,promotional,automation,"The creative velocity system — see it in 20 minutes","The [SYSTEM_NAME] — see it in [TIMEFRAME]"
-direct,follow-up,pipeline,"Next step on the creative bottleneck","Next step on [TOPIC_FROM_CALL]"
-direct,re-engagement,pipeline,"Still thinking about [TOPIC]?","Still thinking about [TOPIC]?"
-direct,cold,education,"How to test 5x more creative concepts per month","How to [DESIRED_OUTCOME] without [COST_OR_EFFORT]"
-direct,cold,pipeline,"The follow-up system that closes stalled deals","The [SYSTEM_TYPE] that [DESIRED_OUTCOME]"
-direct,nurture,education,"The 3-step creative intelligence framework","The [N]-step [FRAMEWORK_NAME]"
-curiosity,nurture,growth-system,"Most businesses that plateau have this in common","Most [AUDIENCE_TYPE]s that [PROBLEM_STATE] have this in common"
-curiosity,cold,results,"What happened when we looked at 100 failing creative programs","What happened when we [ANALYZED_ACTION] [AUDIENCE_CONTEXT]"
-social-proof,nurture,automation,"The weekly testing rhythm that changed the math on creative ROI","The [CADENCE/SYSTEM] that changed the math on [METRIC]"
-social-proof,cold,growth-system,"Why some brands are compounding while others are stuck","Why some [PERSONA_TYPE]s are [SUCCESS_STATE] while others are [STUCK_STATE]"
-urgency,nurture,growth-system,"The gap between you and [desired outcome] is growing","The gap between you and [DESIRED_OUTCOME] is growing"
-urgency,re-engagement,automation,"Your competitors aren't waiting on creative production","Your [COMPETITION_TYPE]s aren't waiting on [BOTTLENECK]"
-personal,cold,pipeline,"[First Name] — one question about your pipeline","[FIRST_NAME] — one question about your [ASSET]"
-personal,re-engagement,results,"[First Name] — thought of you when I saw this","[FIRST_NAME] — thought of you when I saw [CONTEXT]"
-curiosity,nurture,pipeline,"The revenue that's already in your list (most people miss it)","The [ASSET] that's already in your [CHANNEL] (most people miss it)"
-direct,promotional,results,"See the creative OS in action — book your walkthrough","See [SYSTEM_NAME] in action — book your [CTA_TYPE]"
-curiosity,cold,growth-system,"What a $500K/month ad account looks like on the inside","What a [METRIC] [PERSONA_TYPE] looks like on the inside"
-social-proof,nurture,pipeline,"How one follow-up sequence recovered $40K in stalled pipeline","How one [ASSET_TYPE] recovered [METRIC] in [PROBLEM_STATE]"
-personal,nurture,results,"[First Name], this worked for someone in your exact situation","[FIRST_NAME], this worked for someone in your exact situation"
-urgency,cold,automation,"The creative production model is changing — are you ahead of it?","The [INDUSTRY/PROCESS] is changing — are you ahead of it?"

package/assets/worker-kits/growthub-email-marketing-v1/templates/project.md

@@ -1,48 +0,0 @@
----
-# .growthub-fork/project.md — session memory primitive (v1)
-#
-# Written by the CLI at init/import time. Append-only, human-readable; sits
-# alongside the machine-readable `trace.jsonl`. Approvals, self-eval outcomes,
-# and sub-skill runs all record here.
-#
-# Replaceable tokens (seeded at init time):
-#   {{KIT_ID}}   {{FORK_ID}}   {{STARTED_AT}}   {{SOURCE}}   {{SOURCE_REF}}
-
-kitId: "{{KIT_ID}}"
-forkId: "{{FORK_ID}}"
-startedAt: "{{STARTED_AT}}"
-source: "{{SOURCE}}"
-sourceRef: "{{SOURCE_REF}}"
-skillManifestVersion: 1
-approvals: []
-selfEvalHistory: []
-subSkillRuns: []
----
-
-# Project journal — fork `{{FORK_ID}}`
-
-Baseline primitive: `{{KIT_ID}}`. Seeded at `{{STARTED_AT}}` from `{{SOURCE}}` (`{{SOURCE_REF}}`).
-
-This is your cross-session continuity surface. Read the last few entries before every session; append after every material change, approval, and self-eval boundary.
-
-## How to use this file
-
-1. **Session start.** Read the last 3 entries + tail 20 events in `.growthub-fork/trace.jsonl`. State your plan.
-2. **Material change.** Record as a dated bullet (what, why, outcome). Simultaneously append a typed event to `trace.jsonl` via the Fork Sync Agent — never bypass.
-3. **Approval boundary.** Add a row to `approvals` in the frontmatter (verbatim decision).
-4. **Self-eval boundary.** Append to `selfEvalHistory`: `attempt`, `criteria`, `outcome`, `notes`. Enforce `maxRetries: 3`.
-5. **Sub-skill spawn.** Append to `subSkillRuns`: `subSkill`, `startedAt`, `result`.
-
-## Session log
-
-<!-- Append newest entries at the bottom. Format:
-
-### {{YYYY-MM-DD HH:mm UTC}} · {{skill-slug}}
-- **Plan.** What you intend to do.
-- **Changes.** Material changes (each must correspond to a trace event).
-- **Outcome.** Pass / fail / parked. Reference self-eval criteria.
-- **Next.** What the next session should pick up.
-
--->
-
-_No sessions recorded yet. Populated as the fork is operated._

package/assets/worker-kits/growthub-email-marketing-v1/templates/qa-checklist.md

@@ -1,106 +0,0 @@
-# Pre-Send QA Checklist
-
-> Run this checklist on every email before platform upload or send.
-> File naming: attach to campaign folder or reference inline in the campaign brief.
-
----
-
-## CHECKLIST METADATA
-
-```
-CAMPAIGN:     [campaign name]
-CLIENT:       [client slug]
-EMAIL:        [N of N / or "All emails in sequence"]
-REVIEWED BY:  [name or agent]
-REVIEW DATE:  YYYY-MM-DD
-```
-
----
-
-## COPY REVIEW
-
-### Subject line & preview
-
-- [ ] Subject line is written (confirmed from subject line matrix)
-- [ ] A/B test pairing selected — Variant A and Variant B both confirmed
-- [ ] Preview text is written and does NOT repeat the subject line
-- [ ] Subject line is under 50 characters (check for mobile)
-- [ ] No spam trigger words in subject line (FREE!!!, Act NOW, Guaranteed, 100% off)
-- [ ] No ALL CAPS in subject line (except intentional single-word emphasis if brand-approved)
-
-### Body copy
-
-- [ ] Opening hook earns the scroll — specific, not generic
-- [ ] Each body block covers one idea (no idea-stacking)
-- [ ] Sentences are short and scannable (max 2 lines before a break)
-- [ ] Voice and tone matches brand kit adjectives
-- [ ] No approved phrases from brand kit were missed (check brand kit `approved_phrases`)
-- [ ] No messaging guardrail violations (check brand kit `messaging_guardrails`)
-- [ ] No fabricated proof points or unattributed statistics
-- [ ] No hype language: "revolutionary", "game-changing", "best-in-class"
-- [ ] No vague promises: "grow your business", "scale to the moon"
-
-### CTA review
-
-- [ ] One primary CTA per email
-- [ ] CTA text is verb-first and outcome-specific
-- [ ] CTA is on its own line (not buried in paragraph)
-- [ ] CTA URL is confirmed live and correct
-- [ ] PS line is present and reinforces primary CTA or adds secondary angle
-- [ ] For promotional emails: CTA appears above fold AND in PS
-
-### Plain-text fallback
-
-- [ ] Plain-text version is written
-- [ ] All links are plain URLs (no hyperlinked text in plain text)
-- [ ] Plain text is readable and complete without HTML formatting
-
----
-
-## COMPLIANCE REVIEW
-
-- [ ] Unsubscribe link is present in footer
-- [ ] Physical mailing address is present in footer
-- [ ] CAN-SPAM footer format matches brand kit `unsubscribe_footer`
-- [ ] Any proof claims include required disclaimers (check brand kit `compliance_notes`)
-- [ ] "Guaranteed" language is NOT used without the approved qualifier
-- [ ] GDPR: This list has a legitimate opt-in basis (if applicable)
-
----
-
-## PLATFORM REVIEW
-
-- [ ] Sender name matches brand kit `email_from_name`
-- [ ] Sender email matches brand kit `email_from_address`
-- [ ] Segment tag or list is correct for this email
-- [ ] Send delay is set correctly (Day X of sequence)
-- [ ] A/B test variants are both uploaded (if testing)
-- [ ] Platform slot map is complete (if API handoff was used)
-- [ ] Test send has been triggered and reviewed in inbox
-- [ ] Email renders correctly on mobile (check test send)
-- [ ] Email renders correctly on desktop (check test send)
-- [ ] All links work in the test send (click each one)
-
----
-
-## FINAL SIGN-OFF
-
-- [ ] Campaign brief confirmed before this email was written
-- [ ] Sequence plan confirmed before this email was written
-- [ ] Subject line matrix complete for this email
-- [ ] All checklist items above are checked
-- [ ] Deliverables log has been updated in the brand kit
-
-**Sign-off by:** [name]  
-**Date:** YYYY-MM-DD  
-**Status:** APPROVED TO SEND / NEEDS REVISION
-
----
-
-## REVISION LOG
-
-> If revisions are needed, log them here before re-running checklist.
-
-| Date | Item | Issue | Resolution |
-|---|---|---|---|
-| | | | |

package/assets/worker-kits/growthub-email-marketing-v1/templates/self-eval.md

@@ -1,67 +0,0 @@
-# Self-evaluation template — v1 primitive (Growthub, capability-agnostic)
-
-A skill's `selfEval` contract declares **what good looks like** (`criteria[]`) and **the retry ceiling** (`maxRetries`). The agent drives the loop; this file is the pattern the agent follows at every unit of work.
-
-The contract is defined in `@growthub/api-contract/skills::SkillSelfEval` and is **capability-agnostic** — the same primitive applies to code edits, copy drafts, CRM rules, API payloads, asset renders, audit passes, and every other domain. The "unit of work" is the smallest reversible change the skill operates on; concrete boundaries are defined in the kit's own `skills.md` operator runbook, not here.
-
-## Loop
-
-```
-for attempt in 1..maxRetries:          # default maxRetries = 3
-  generate       — produce a proposal (whatever the skill produces)
-  apply          — materialise the proposal against the fork
-  self-evaluate  — for each criterion in skill.selfEval.criteria:
-                     check → pass / fail / needs-confirmation
-  record         — append to project.md (human) + trace.jsonl (machine)
-
-  if all criteria pass: break
-  if attempt == maxRetries: park with needs_confirmation note. Stop.
-```
-
-## What each attempt writes
-
-### Human row — append to `.growthub-fork/project.md` "Session log"
-
-```md
-### 2026-04-23 18:40 UTC · <skill-slug>
-- **Plan.** What you intend to do this unit of work.
-- **Changes.** Material change applied (must correspond to a trace event).
-- **Self-eval.** attempt 2/3 — criterion "<one of skill.selfEval.criteria>" ✗ (<note>). Retrying.
-- **Outcome.** retry-pending / pass / parked.
-- **Next.** What the next attempt (or next session) should pick up.
-```
-
-### Machine row — append to `.growthub-fork/trace.jsonl` (via `appendKitForkTraceEvent`)
-
-```json
-{
-  "ts": "2026-04-23T18:40:00.000Z",
-  "forkId": "<fork-id>",
-  "kitId": "<kit-id>",
-  "type": "self_eval_recorded",
-  "summary": "attempt 2/3 failed on <criterion>",
-  "detail": {
-    "skill": "<skill-slug>",
-    "attempt": 2,
-    "maxRetries": 3,
-    "criterion": "<one of skill.selfEval.criteria>",
-    "outcome": "fail",
-    "notes": "<short explanation>"
-  }
-}
-```
-
-## Hard rules
-
-1. **Never exceed `maxRetries`.** At the ceiling, park with a `needs_confirmation` note and stop. Do not loop forever.
-2. **Record every attempt.** Even the first pass. Continuity depends on a complete journal.
-3. **Keep `project.md` and `trace.jsonl` in sync.** One without the other is a protocol violation.
-4. **Preserve prior entries.** Append-only. Never rewrite history.
-
-## Bound the blast radius
-
-Evaluate at the smallest unit of work the skill operates on, not only at the end of a multi-step run. The retry ceiling applies to that unit — so a bad attempt does not sink the whole job.
-
-What counts as a "unit of work" is **kit-specific** and lives in that kit's `skills.md` operator runbook — not in this agnostic template. A kit picks its own smallest reversible boundary and documents it in `skills.md`; this template does not prescribe one.
-
-The agnostic SDK (`@growthub/api-contract/skills::SkillSelfEval`) does not encode any domain-specific boundaries — it only carries `criteria[]`, `maxRetries`, and `traceTo`. See `SKILL.md::selfEval.criteria` in this kit for the concrete checks, and `skills.md` for the kit-specific unit of work.

package/assets/worker-kits/growthub-email-marketing-v1/templates/sequence-planner.md

@@ -1,94 +0,0 @@
-# Sequence Planner
-
-> Use this to map the full arc of any email sequence before writing individual drafts.
-> One row per email. Complete the full table before opening `email-draft.md`.
-
----
-
-## SEQUENCE IDENTITY
-
-| Field | Value |
-|---|---|
-| **Sequence name** | |
-| **Campaign type** | nurture / cold outbound / follow-up / re-engagement / promotional |
-| **Content pillar** | |
-| **Audience segment** | |
-| **Entry trigger** | |
-| **Total emails** | |
-| **Total duration** | |
-
----
-
-## SEQUENCE MAP
-
-| # | Send Day | Theme | Opening Hook (1 sentence) | Body Arc | Primary CTA | Secondary CTA | Platform Tag |
-|---|---|---|---|---|---|---|---|
-| 1 | Day 0 | | | | | | |
-| 2 | Day +X | | | | | | |
-| 3 | Day +X | | | | | | |
-| 4 | Day +X | | | | | | |
-| 5 | Day +X | | | | | | |
-
----
-
-## ARC NOTES
-
-**Overall arc (in one sentence):**
-> [e.g. Takes a frustrated DTC buyer from creative bottleneck pain → understanding the Creative OS → booking a growth call]
-
-**Pillar angle:**
-> [e.g. Pillar 2 — Automation & AI — angle: the bottleneck isn't your team, it's the gap between ideas and execution]
-
-**Tone shift across sequence:**
-> [e.g. Email 1–2: empathetic, problem-naming / Email 3: educational / Email 4–5: proof + activation]
-
-**What the sequence does NOT do:**
-> [e.g. Does not push for a call in Email 1. Does not mention pricing. Does not use urgency until Email 4.]
-
----
-
-## PILLAR-TO-BODY-ARC MAPPING
-
-Use this reference when filling the Body Arc column:
-
-| Pillar | Body arc options |
-|---|---|
-| Growth System | Problem naming → infrastructure gap → what systematic looks like → CTA |
-| Automation & AI | Speed problem → mechanism reveal → what's possible → CTA |
-| Client Results | Relatable situation → what happened → proof → how you can do it → CTA |
-| Education & Strategy | Question/curiosity → framework → implementation tip → CTA |
-| Pipeline & Revenue | Stall diagnosis → re-engagement angle → urgency → CTA |
-
----
-
-## MODULE SELECTION GUIDE
-
-For each email, select the body blocks that match the arc. Check `templates/email-modules/INDEX.md`.
-
-| Body arc step | Module to use |
-|---|---|
-| Problem naming / pain | `body/problem-agitate.md` |
-| Mechanism / insight reveal | `body/value-reveal.md` |
-| Client story / proof bridge | `body/story-bridge.md` |
-| Framework / how-to | `body/education-block.md` |
-| Book call / demo CTA | `cta/primary-cta.md` |
-| Reply / resource soft ask | `cta/soft-cta.md` |
-| Conversational reply ask | `cta/reply-cta.md` |
-| Curiosity subject line | `subject-lines/curiosity.md` |
-| Proof-anchored subject line | `subject-lines/social-proof.md` |
-| Urgency subject line | `subject-lines/urgency.md` |
-| Personalized subject line | `subject-lines/personal.md` |
-
----
-
-## SEND CADENCE REFERENCE
-
-| Campaign type | Default cadence |
-|---|---|
-| Nurture (5 emails) | Day 0 / +3 / +6 / +10 / +14 |
-| Cold outbound (4 emails) | Day 0 / +2 / +5 / +9 |
-| Follow-up (3 emails) | Day 0 / +1 / +3 |
-| Re-engagement (3 emails) | Day 0 / +5 / +10 |
-| Promotional broadcast (1) | Single send — set send date |
-
-> Adjust based on audience and client preference. Document any changes in the campaign brief.

package/assets/worker-kits/growthub-email-marketing-v1/templates/subject-line-matrix.md

@@ -1,136 +0,0 @@
-# Subject Line Matrix
-
-> One matrix per campaign (or per email if testing intensively).
-> Minimum 5 variants per email. Always include preview text.
-> File naming: `<ClientSlug>_SubjectLineMatrix_v<N>_<YYYYMMDD>.md`
-
----
-
-## MATRIX METADATA
-
-```
-CAMPAIGN:     [campaign name]
-CLIENT:       [client slug]
-PILLAR:       [anchor pillar]
-SEGMENT:      [target segment]
-VERSION:      v1
-DATE:         YYYY-MM-DD
-```
-
----
-
-## HOW TO USE THIS MATRIX
-
-1. Write 5+ variants per email — at least one per type (curiosity / urgency / proof / personal)
-2. Always pair subject line with preview text
-3. Select the recommended A/B test pairing at the bottom
-4. Upload both variants to the platform and split-test on open rate
-5. Log results in the deliverables log
-
-**Subject line type guide:**
-
-| Type | What it does | Best used for |
-|---|---|---|
-| Curiosity | Opens a loop — reader must open to close it | Nurture, educational, cold |
-| Social Proof | Anchors credibility with a result or number | Client results, warm nurture, promo |
-| Urgency | Creates a reason to act now | Promotional, follow-up, re-engagement |
-| Personal | Speaks directly to the individual — their situation | Cold outbound, re-engagement |
-| Direct | States the value plainly — no hooks | Re-engagement, warm audiences who trust the brand |
-
----
-
-## EMAIL 1 — [THEME]
-
-> Theme: [theme name] | Send Day: Day 0 | Pillar: [pillar]
-
-| # | Type | Subject Line | Preview Text | Notes |
-|---|---|---|---|---|
-| 1A | Curiosity | [subject line] | [preview text] | [notes] |
-| 1B | Social Proof | [subject line] | [preview text] | [notes] |
-| 1C | Urgency | [subject line] | [preview text] | [notes] |
-| 1D | Personal | [subject line] | [preview text] | [notes] |
-| 1E | Direct | [subject line] | [preview text] | [notes] |
-
-**Recommended A/B test:** `1A` vs `1D`  
-**Rationale:** [why this pairing makes sense for this audience + stage]
-
----
-
-## EMAIL 2 — [THEME]
-
-> Theme: [theme name] | Send Day: Day +3 | Pillar: [pillar]
-
-| # | Type | Subject Line | Preview Text | Notes |
-|---|---|---|---|---|
-| 2A | Curiosity | [subject line] | [preview text] | [notes] |
-| 2B | Social Proof | [subject line] | [preview text] | [notes] |
-| 2C | Urgency | [subject line] | [preview text] | [notes] |
-| 2D | Personal | [subject line] | [preview text] | [notes] |
-| 2E | Direct | [subject line] | [preview text] | [notes] |
-
-**Recommended A/B test:** `2A` vs `2C`  
-**Rationale:** [rationale]
-
----
-
-## EMAIL 3 — [THEME]
-
-> Theme: [theme name] | Send Day: Day +6 | Pillar: [pillar]
-
-| # | Type | Subject Line | Preview Text | Notes |
-|---|---|---|---|---|
-| 3A | Curiosity | [subject line] | [preview text] | [notes] |
-| 3B | Social Proof | [subject line] | [preview text] | [notes] |
-| 3C | Urgency | [subject line] | [preview text] | [notes] |
-| 3D | Personal | [subject line] | [preview text] | [notes] |
-| 3E | Direct | [subject line] | [preview text] | [notes] |
-
-**Recommended A/B test:** `3B` vs `3D`  
-**Rationale:** [rationale]
-
----
-
-## EMAIL 4 — [THEME]
-
-> Theme: [theme name] | Send Day: Day +10 | Pillar: [pillar]
-
-| # | Type | Subject Line | Preview Text | Notes |
-|---|---|---|---|---|
-| 4A | Curiosity | [subject line] | [preview text] | [notes] |
-| 4B | Social Proof | [subject line] | [preview text] | [notes] |
-| 4C | Urgency | [subject line] | [preview text] | [notes] |
-| 4D | Personal | [subject line] | [preview text] | [notes] |
-| 4E | Direct | [subject line] | [preview text] | [notes] |
-
-**Recommended A/B test:** `4C` vs `4D`  
-**Rationale:** [rationale]
-
----
-
-## EMAIL 5 — [THEME]
-
-> Theme: [theme name] | Send Day: Day +14 | Pillar: [pillar]
-
-| # | Type | Subject Line | Preview Text | Notes |
-|---|---|---|---|---|
-| 5A | Curiosity | [subject line] | [preview text] | [notes] |
-| 5B | Social Proof | [subject line] | [preview text] | [notes] |
-| 5C | Urgency | [subject line] | [preview text] | [notes] |
-| 5D | Personal | [subject line] | [preview text] | [notes] |
-| 5E | Direct | [subject line] | [preview text] | [notes] |
-
-**Recommended A/B test:** `5B` vs `5C`  
-**Rationale:** [rationale]
-
----
-
-## SUBJECT LINE RULES (NON-NEGOTIABLE)
-
-- Maximum 50 characters for mobile preview — test at 40 if unsure
-- No ALL CAPS (except a single word for emphasis, used sparingly)
-- No spam trigger words: "FREE!!!", "Act NOW", "Guaranteed", "100% free"
-- Preview text never repeats the subject line — it extends or reframes it
-- Question subject lines only if the question is genuinely unexpected
-- First-name personalization (`[First Name],`) used only in cold/personal sequences
-- Emoji is brand-specific — check brand kit before using
-- Every subject line in the matrix must be genuinely different — not just word swaps