Lifecycle nurture orchestration across segments with automation builds and optimization
Installation
npx claude-plugins install @gtmagents/gtm-agents/lead-nurture-orchestration
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 3 skill definitions:
lifecycle-cadence
Use when defining nurture pacing, triggers, and suppression logic.
View skill definition
Lifecycle Cadence Systems Skill
When to Use
- Designing new nurture programs or refreshing existing cadences.
- Auditing fatigue, suppression, or timing conflicts across journeys.
- Coordinating MAP and CRM routing for multi-channel touches.
Framework
- Lifecycle Stage Alignment – ensure cadence matches funnel stage (MQL, SAL, SQL, post-sale).
- Trigger Definition – entry signals (form fills, intent spikes, product milestones, campaign responses).
- Pacing Rules – waiting periods, fallback content, stop logic for engagement or conversions.
- Suppression & Priority – handle conflicting journeys, global caps, sales stages, manual pauses.
- Monitoring – alerts for high unsubscribe/bounce, low engagement, or SLA breaches.
Templates
- Cadence planner (stage, delay, channel, CTA, exit criteria).
- Suppression matrix (journey priority, conflicts, resolution rules).
- Monitoring checklist (metrics, thresholds, escalation owners).
Tips
- Reassess cadences quarterly as product/offers evolve.
- Keep a single decision table for suppression rules to avoid MAP drift.
- Align with sales/CS to pause nurtures when opps advance or risks arise.
nurture-testing
Use when planning, executing, and logging nurture experiments and regression
View skill definition
Nurture Testing & QA Skill
When to Use
- Running experiments (subject lines, timing, offers, personalization) in nurture flows.
- Performing regression tests before go-live or updates.
- Documenting QA evidence for compliance/audits.
Framework
- Test Design – hypothesis, variable, control, variant, KPI, sample size, duration.
- QA Checklist – links, tokens, segmentation, tracking, device/browser coverage, accessibility.
- Evidence Logging – screenshots, seed inbox captures, MAP logs, CRM task verification.
- Significance & Rollout – evaluation method (frequentist/Bayesian), rollout criteria, holdback rules.
- Regression Cadence – schedule for periodic audits, triggered when assets/tokens change.
Templates
- Experiment brief + tracker.
- QA matrix (scenario, expected result, status, owner).
- Evidence archive folder structure.
Tips
- Always include control groups or holdouts for long-running nurtures.
- Automate reminders to re-run QA after major MAP/CRM updates.
- Pair with
personalization-logicandmarketing-ops-partnerto catch edge cases early.
personalization-logic
Use when defining dynamic content rules, tokens, and conditional offers
View skill definition
Nurture Personalization Logic Skill
When to Use
- Building dynamic content for lifecycle nurtures.
- Mapping personalization tokens (industry, role, behavior) to copy blocks.
- Coordinating personalization across email, in-app, ads, and SDR assists.
Framework
- Segmentation Inputs – persona, industry, product usage, lifecycle stage, engagement history.
- Content Blocks – hero, proof, CTA, offer modules with variants per segment.
- Token Management – define data sources, fallback values, formatting rules.
- Testing Plan – structure A/B/C tests for personalization depth.
- Governance – approval workflows, localization, compliance, expirations.
Templates
- Personalization matrix (segment vs module vs asset).
- Token dictionary (field, source, fallback, formatting).
- QA checklist (seed records, fallback coverage, compliance notes).
Tips
- Start with modular blocks so ops can update without rewriting entire emails.
- Document dependencies on upstream data hygiene.
- Pair with
copywriting+designteams for brand consistency.