Skip to content

gooseworks-ai/goose-skills / skills/marketing/email-lifecycle

email-lifecycle

Verified

Lifecycle email, SMS and push: audits the list and deliverability, then writes the flows this kind of business needs first, loadable as-is in your own tool, plus segments, cadence and this week's broadcasts. Never sends anything. Use when: set up my welcome and abandoned-cart emails; trial onboarding or waitlist launch emails; win back lapsed customers; plan this week's emails and texts; push notifications for my app; why are my emails going to spam; plan our Black Friday email and SMS sends; a send went wrong. Not for cold outreach to prospects — use write-outreach; not the editorial newsletter issue — use make-content; not the whole cross-channel Black Friday plan — use plan-campaign.

skill.meta.json

View on GitHub
{
  "slug": "email-lifecycle",
  "category": "playbooks",
  "tier": "playbook",
  "version": "0.1.1",
  "tags": [
    "content",
    "outreach"
  ],
  "collections": [
    "brand-growth"
  ],
  "collection_stage": "create",
  "requires_skills": [
    "ad-policy-check",
    "claims-gate",
    "email-lifecycle-broadcast-planner",
    "email-lifecycle-flow-writer",
    "email-lifecycle-lifecycle-audit",
    "email-lifecycle-offer-math",
    "email-lifecycle-send-check",
    "marketing-data-access",
    "marketing-guide",
    "run-memory",
    "save-learning",
    "save-to-brain",
    "spend-gate",
    "voice-card",
    "write-report"
  ],
  "pillar": "7 — Email, SMS and lifecycle (with the lifecycle bullets of 21 messaging and 22 growth loops)",
  "intents": [
    "set up my welcome and abandoned-cart emails",
    "my email list just sits there",
    "write my email flows",
    "plan this week's emails and texts",
    "win back lapsed customers",
    "post-purchase, review request and referral emails",
    "trial onboarding emails for my SaaS",
    "push notifications and in-app messages for my app",
    "why are my emails going to spam",
    "launch emails for my waitlist",
    "plan our Black Friday sends",
    "a send went wrong, help me fix it"
  ],
  "reads": [
    "brand brain — brand_knowledge_browse core and required reads, then chapters 2, 5, 11, 15, 17, 18, 20, brand_knowledge_read and brand_knowledge_search for gaps when brand_knowledge_* tools are listed; else brand_read summary, kit, products (price, offers, notes), learnings (server research and the app; learn-my-brand, unreleased)",
    "claims — the shared claims-gate atom over the sign-off contract (signed-off marker → 'Claims you may use' facts; written by its scoped sign-off, or earlier by learn-my-brand, unreleased)",
    "standing offer and brand-wide policies — the shared Standing offer: fact, any Policy: facts (written earlier by learn-my-brand, unreleased) and earlier [lifecycle] rules, else the Brand record",
    "voice and banned words — brand learnings (server research and the app; learn-my-brand, unreleased); voice cards brand/voices/<handle>.md via the shared voice-card atom (make-content, run-organic-social)",
    "weekly performance read — reports/performance/<date>.md (analyze-performance)",
    "campaign brief with an email/SMS leg — campaign_read (plan-campaign)",
    "review-request brief — 'For your email program — review requests' section of search/fixes/<date>.md (improve-search-visibility)",
    "newsletter issue — content/newsletter/<date>.md (make-content)",
    "program sheet from earlier runs — lifecycle/program.md (this playbook)",
    "email tool exports, a recent campaign's 'original' text, spam-rate screenshot, margins, stock — human-provided",
    "'Graphic ready:' answers under its own header-art request lines in lifecycle/flows/ (make-static-ads)",
    "last run record — newest of runs/email-lifecycle/<job>/<date>.md via the shared run-memory atom (this playbook's earlier runs)"
  ],
  "writes": [
    "the email program pack — local file gooseworks-reports/<brand-slug>/<YYYY-MM-DD>-email-program.md (or an artifact in hosted chat) through the shared write-report atom, plus a saved copy with a link (read by the marketer)",
    "lifecycle/program.md + brand document 'Lifecycle program — <Brand> — <date>' (supersede) — program sheet with each flow's hypothesis, target and last result (read by the next run's read-back and the human; others through knowledge_search)",
    "lifecycle/flows/<flow-slug>.md — flow pack with ready / not-ready status, tracking plan when events are missing (read by the human; header-art request lines for make-static-ads)",
    "lifecycle/calendar/<YYYY-MM>.md — send calendar, interim home for offers (read by the human, the next run and plan-campaign)",
    "lifecycle/broadcasts/<YYYY-MM-DD>.md — this week's broadcasts (read by the human)",
    "lifecycle/deliverability/<YYYY-MM-DD>.md — deliverability report (read by the next run)",
    "optional weekly automation, created paused — automation_upsert (enabled by the human)",
    "brand learnings via the shared save-learning atom, once per run: the shared Standing offer: fact and [lifecycle YYYY-MM-DD] rules, confirmed policies included (human-confirmed; never Policy: facts, a fixed opening no released playbook writes; read by every playbook)",
    "scoped claims sign-off when needed, through the shared claims-gate atom: a Brand record version, 'Claims you may use' facts and the marker (read by every copy-writing playbook)",
    "run record — runs/email-lifecycle/<job-slug>/<YYYY-MM-DD>.md + brand document 'Run record — <job> — <Brand> — <date>' (keep-history) via the shared run-memory atom (read by the next run of any email job)"
  ],
  "needs": {
    "mcp": [
      "gooseworks:get_started",
      "gooseworks:tools_load",
      "gooseworks:brand_read",
      "gooseworks:brand_update",
      "gooseworks:campaign_read",
      "gooseworks:file_read",
      "gooseworks:file_list",
      "gooseworks:file_write",
      "gooseworks:automation_upsert",
      "gooseworks:file_url",
      "gooseworks:media_upload",
      "gooseworks:knowledge_import",
      "gooseworks:job_get",
      "gooseworks:media_list",
      "gooseworks:media_update",
      "gooseworks:knowledge_search",
      "gooseworks:automation_list",
      "gooseworks:brand_knowledge_browse",
      "gooseworks:brand_knowledge_read",
      "gooseworks:brand_knowledge_search"
    ]
  }
}
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall