Lifecycle email orchestration for planning, automating, and analyzing multi-touch sequences
Installation
npx claude-plugins install @gtmagents/gtm-agents/email-sequence-orchestration
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 2 skill definitions:
cadence-design
Use when spacing, sequencing, and pacing multi-touch email programs.
View skill definition
Email Cadence Design Skill
When to Use
- Planning nurture, onboarding, or expansion sequences with multiple branches.
- Auditing send frequency to reduce fatigue and unsubscribes.
- Coordinating cross-channel touches (email, in-app, SMS, sales assist).
Framework
- Goal Alignment – map KPIs per stage (activation, education, expansion, retention).
- Signal-Based Timing – trigger on behavior (opens, clicks, product events), not fixed delays.
- Frequency Guardrails – define daily/weekly send caps per persona + lifecycle stage.
- Channel Mix – pair emails with supporting channels; document ownership and SLAs.
- Recovery Paths – add detours for inactivity, hard bounces, or sales handoffs.
Templates
- Cadence matrix (day, trigger, message purpose, CTA, channel).
- Fatigue model calculator (touches vs engagement trend).
- Suppression logic checklist (recent send, opportunity stage, consent).
Tips
- Front-load value but leave whitespace before high-ask CTAs.
- Reuse proven send windows per persona while testing incrementally.
- Share cadence plan with SDR/CSM teams to prevent overlap.
qa-gates
Use before launching sequences to validate content, data, compliance,
View skill definition
Email QA Gates Skill
When to Use
- Prior to activating new nurture or lifecycle programs.
- After major changes to segmentation, personalization tokens, or deliverability settings.
- During post-incident reviews to ensure fixes remain in place.
Framework
- Content & Personalization – placeholders resolved, links tracked, dynamic content fallback tested.
- Data & Routing – trigger logic, smart lists, suppression rules, CRM fields synced.
- Compliance – footer language, preference center links, consent status, regional routing.
- Tracking & Analytics – UTM/tagging consistency, BI/warehouse pipes, alert webhooks.
- Monitoring Hooks – dashboards referenced, alert thresholds set, rollback plan documented.
Templates
- QA runbook with owner, status, evidence links for each checklist item.
- Proofing matrix (persona × email × device × ISP) for screenshot validation.
- Launch readiness form requiring sign-off from marketing, ops, legal, and RevOps.
Tips
- Pair with
deliverability-opsto confirm authentication and inbox monitoring. - Automate regression tests via API where possible (token validation, link health).
- Store QA evidence (screenshots, logs) alongside sequence assets for audits.