email-sequence-designer

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: email-sequence-designer
slug: aaron-email-sequence-designer
displayName: "Email Sequence Designer · 邮件自动化流程设计"
summary: "邮件自动化流程设计/购物车挽回/流失召回序列"
description: 'Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-specialist; not for writing each email''s copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列'
version: "19.2.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use when designing or restructuring general email lifecycle automation before writing the individual emails: a welcome onboarding series, an abandoned-cart or browse-abandon flow, a post-purchase / replenishment sequence, a light in-flow re-engagement branch, a B2B cold-outbound multi-step sequence, or the program's overall frequency governance and sunset policy. Activate when the user has a lifecycle stage, trigger event, or list-fatigue problem and wants the flow map, cadence, and branch/exit logic before creative or send-testing begins. Not for the closed-loop win-back / re-consent (re-permission) program on a defined lapsed cohort — that self-contained recovery-or-retire program is reactivation-specialist's."
argument-hint: "<flow type or lifecycle goal> [platform/ESP] [trigger event] [audience/segment]"
metadata: {"author": "aaron-he-zhu", "version": "19.2.0", "discipline": "email", "phase": "nurture", "geo-relevance": "low", "hermes": {"tags": ["marketing", "email", "nurture"], "category": "email"}, "openclaw": {"emoji": "✉️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---

# Email Sequence Designer

Designs email lifecycle and automation flows plus the program's frequency governance, and scores the SEND **N (Nurture / Lifecycle)** dimension. It maps each flow's trigger, step timing, branch/exit conditions, and goal, layers a global cadence policy (send caps, quiet hours, fatigue guardrail) and a re-engagement/sunset path over the top, then hands the flow map to the skill that writes each step and to the auditor that scores the full program. It covers general lifecycle flows and owns the engagement-decay/sunset sub-item; the closed-loop win-back / re-consent (re-permission) program on a defined lapsed cohort is [reactivation-specialist](../reactivation-specialist/SKILL.md)'s, and the preference-center / frequency-options design is [preference-frequency-manager](../preference-frequency-manager/SKILL.md)'s. It does not write the individual email or compute the final EQS.

## Quick Start

```
Design a welcome flow for [product/audience] on [ESP]. Trigger is [signup event]; here is my current list/segment export: [paste/path].
```

```
Build an abandoned-cart sequence: [N] steps, [timing], with a discount branch and an exit-on-purchase condition.
```

```
My unengaged segment is [X]% of the list and complaints are rising. Design a win-back sequence and a sunset policy with send caps and quiet hours.
```

## Skill Contract

**Expected output**: a set of lifecycle flow maps (trigger, per-step timing, branch/exit conditions, goal per flow), a frequency-governance block (global send cap, quiet hours, fatigue guardrail), a re-engagement/sunset path, a SEND **N** dimension score with sub-item notes and the typed profile named, and the standard handoff summary.

- **Reads**: the flow type or lifecycle