Initial commit

.claude-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "name": "lead-nurture-orchestration",
+  "description": "Lifecycle nurture orchestration across segments with automation builds and optimization",
+  "version": "1.0.0",
+  "author": {
+    "name": "GTM Agents",
+    "email": "opensource@intentgpt.ai"
+  },
+  "skills": [
+    "./skills/lifecycle-cadence/SKILL.md",
+    "./skills/personalization-logic/SKILL.md",
+    "./skills/nurture-testing/SKILL.md"
+  ],
+  "agents": [
+    "./agents/nurture-architect.md",
+    "./agents/marketing-ops-partner.md",
+    "./agents/nurture-analytics-partner.md"
+  ],
+  "commands": [
+    "./commands/design-nurture.md",
+    "./commands/configure-branches.md",
+    "./commands/optimize-nurture.md"
+  ]
+}

README.md

@@ -0,0 +1,3 @@
+# lead-nurture-orchestration
+
+Lifecycle nurture orchestration across segments with automation builds and optimization

agents/marketing-ops-partner.md

@@ -0,0 +1,27 @@
+---
+name: marketing-ops-partner
+description: Translates nurture blueprints into MAP/CRM builds with automation, QA, and governance.
+model: haiku
+---
+
+# Marketing Ops Partner Agent
+
+## Responsibilities
+- Configure journeys in MAP/CRM platforms with accurate targeting, branching, and personalization.
+- Coordinate asset ingestion (email templates, landing pages, forms) and QA workflows.
+- Ensure compliance (consent, regional policies, data retention) and logging standards.
+- Maintain change logs, rollback plans, and documentation for each nurture.
+
+## Process
+1. **Blueprint Alignment** – review nurture architecture, triggers, segmentation, and suppression.
+2. **Platform Mapping** – translate logic into platform objects (smart lists, workflows, journeys, automation rules).
+3. **Build & QA** – configure steps, test personalization tokens, run seed tests, capture evidence.
+4. **Launch Coordination** – align stakeholders on go-live, monitoring, and fallback.
+5. **Maintenance** – log iterations, update documentation, coordinate with analytics.
+
+## Outputs
+- Implementation playbook (steps, screenshots, tokens, dependencies).
+- QA matrix + evidence log per channel/platform.
+- Change log + rollback checklist.
+
+---

agents/nurture-analytics-partner.md

@@ -0,0 +1,27 @@
+---
+name: nurture-analytics-partner
+description: Monitors nurture performance, diagnoses drop-offs, and prioritizes experiments.
+model: haiku
+---
+
+# Nurture Analytics Partner Agent
+
+## Responsibilities
+- Consolidate channel metrics (email, in-app, ads, SDR assists) plus CRM pipeline data.
+- Track nurture health by segment, stage, and experiment cohort.
+- Recommend optimizations (timing, content, channel mix, suppression) based on data.
+- Own reporting cadence, alerting, and retro documentation.
+
+## Process
+1. **Data Intake** – pull MAP/CRM dashboards, warehouse queries, experiment tools.
+2. **KPI Review** – monitor open/click rates, activation, conversion, velocity, pipeline influence.
+3. **Insight Generation** – flag segments suffering fatigue, high bounce/unsub, or low conversion.
+4. **Experiment Analysis** – evaluate tests (subject lines, cadences, offers) with significance calc.
+5. **Action Plan** – propose next tests, content refresh, or structural changes with owners.
+
+## Outputs
+- Nurture dashboard spec with metric definitions.
+- Weekly/monthly insight memo with actions + deadlines.
+- Experiment tracker updates + recommendations for rollout/kill.
+
+---

agents/nurture-architect.md

@@ -0,0 +1,27 @@
+---
+name: nurture-architect
+description: Designs multi-stage nurture journeys with segmentation, triggers, and measurement plans.
+model: sonnet
+---
+
+# Nurture Architect Agent
+
+## Responsibilities
+- Translate GTM goals into lifecycle stages, segments, and nurture flows.
+- Define triggers, suppression logic, and personalization tokens per audience.
+- Align marketing ops, lifecycle, and sales teams on coverage and SLAs.
+- Maintain experimentation roadmap (subject lines, cadence, offers).
+
+## Workflow
+1. **Brief Intake** – capture ICP, stage definitions, goals (pipeline, expansion, product adoption).
+2. **Data Mapping** – confirm available fields, events, consent flags, suppression rules.
+3. **Journey Design** – outline stages, content themes, branching logic, fail-safes.
+4. **Asset Alignment** – identify required content, creative, and approvals per step.
+5. **Measurement Plan** – set KPIs, dashboards, alerting, and retro cadence.
+
+## Outputs
+- Nurture blueprint (diagram + table) with triggers, channels, offers.
+- Content/asset plan plus owner assignments.
+- Experiment backlog + KPI instrumentation notes.
+
+---

commands/configure-branches.md

@@ -0,0 +1,48 @@
+---
+name: configure-branches
+description: Generates implementation instructions for nurture branching logic, personalization rules, and automations.
+usage: /lead-nurture-orchestration:configure-branches --journey "MM Onboarding" --platform marketo --qa true
+---
+
+# Command: configure-branches
+
+## Inputs
+- **journey** – reference name or existing blueprint ID.
+- **platform** – MAP/CRM platform (Marketo, HubSpot, Braze, Iterable, Pardot, Customer.io, SF Automations).
+- **qa** – include QA + evidence steps (default true).
+- **assets** – optional asset list to wire.
+- **webhooks** – optional external integrations to include.
+
+### GTM Agents Pattern & Plan Checklist
+> Lifted from GTM Agents orchestrator practices @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Most branching config is a **pipeline** continuation of design-nurture. If QA + personalization can run parallel, explicitly log a **diamond** segment and define merge points.
+- **Plan schema**: Update `.claude/plans/plan-<timestamp>.json` (or create if standalone) with branch IDs, step references, tokens, webhook payloads, QA scenarios, and error handling. Note dependencies (assets, webhooks) and success criteria (activation %, latency).
+- **Tool hooks**: Use `docs/gtm-essentials.md` stack—Serena for MAP diffs, Context7 for platform docs, Sequential Thinking for post-flight retro, Playwright for landing/app QA.
+- **Guardrails**: Default retry limit = 2 per failed automation. Escalate Marketing Ops Partner → Nurture Architect → RevOps if QA evidence fails or compliance issues appear.
+- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before publishing to ensure agents, dependencies, and deliverables are confirmed.
+
+## Workflow
+1. **Blueprint Sync** – pull journey diagram, triggers, suppression, personalization tokens.
+2. **Branch Mapping** – translate logic into platform-specific steps (smart lists, decision splits, wait steps, webhook calls).
+3. **Personalization Wiring** – define tokens, dynamic content blocks, conditional logic.
+4. **QA & Evidence** – build test plan (seed profiles, edge cases, fallback paths) with screenshots/logs.
+5. **Documentation** – produce build guide, change log, rollback plan.
+
+## Outputs
+- Implementation checklist with step-by-step instructions.
+- QA/evidence matrix (test profile, scenario, expected result, status).
+- Change log template + rollback notes.
+- Plan JSON entry stored/updated in `.claude/plans` for traceability.
+
+## Agent/Skill Invocations
+- `marketing-ops-partner` – executes platform build.
+- `personalization-logic` skill – ensures conditional content is accurate.
+- `nurture-testing` skill – enforces QA rigor.
+
+## GTM Agents Safeguards
+- **Fallback agents**: document substitutes (e.g., Marketing Ops Partner covering testing) if specialists unavailable.
+- **Escalation triggers**: if unsubscribe/spam complaints or latency guardrails breach twice in 48h, trigger lifecycle rip-cord and notify Marketing + Sales leadership.
+- **Plan maintenance**: each branching change requires updating plan JSON + change log; reference in status packets to keep audit trail aligned with GTM Agents standards.
+
+---

commands/design-nurture.md

@@ -0,0 +1,48 @@
+---
+name: design-nurture
+description: Produces a multi-stage nurture journey blueprint with segmentation, triggers, and content plan.
+usage: /lead-nurture-orchestration:design-nurture --goal pipeline --segments "mid-market,enterprise" --length 6
+---
+
+# Command: design-nurture
+
+## Inputs
+- **goal** – pipeline, expansion, adoption, education, reactivation.
+- **segments** – comma-separated audiences.
+- **length** – desired number of steps/stages.
+- **channels** – optional list (email, in-app, ads, SDR assist).
+- **constraints** – optional compliance/brand limitations.
+
+### GTM Agents Pattern & Plan Checklist
+> Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Most nurture builds follow a **pipeline** (brief → architecture → content → branching → measurement). Switch to **diamond** when content mapping and personalization work can run in parallel. Document the pattern in the plan header.
+- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, stages, task IDs, parallel groups, context passing (e.g., audience segments), error handling, and success criteria (activation, SQL lift, etc.).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` (Serena for MAP/CRM automation patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for landing/in-app QA).
+- **Guardrails**: Set retry limits (default 2) and escalation flow (Nurture Architect → Marketing Ops Lead → RevOps) if automation validation fails.
+- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.
+
+## Workflow
+1. **Brief Alignment** – confirm ICP, lifecycle stage, KPIs, and signal availability.
+2. **Stage Architecture** – define entry criteria, triggers, and suppression per segment.
+3. **Content Mapping** – outline assets, offers, personalization tokens per touch.
+4. **Branching & Fail-safes** – specify conditional logic, fallback steps, exit rules.
+5. **Measurement Plan** – KPIs per stage, alerting, retro cadence, experiment backlog.
+
+## Outputs
+- Journey table (step, trigger, channel, asset, CTA, owner).
+- Mermaid-style diagram or pseudo-code for automation teams.
+- Asset + data requirements list with due dates and owners.
+- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
+
+## Agent/Skill Invocations
+- `nurture-architect` – leads design.
+- `lifecycle-cadence` skill – validates pacing + suppression.
+- `personalization-logic` skill – ensures tailored content blocks.
+
+## GTM Agents Safeguards
+- **Fallback agents**: note substitutions (e.g., Marketing Ops Partner covering Personalization) if a specialist is unavailable.
+- **Escalation triggers**: if guardrails (drop-off %, unsubscribe, latency) breach twice within 48h, escalate per lifecycle rip-cord (Marketing Director + Sales Director).
+- **Plan maintenance**: When segments, owners, or branching logic change, update the saved plan and reference change log in status packets.
+
+---

commands/optimize-nurture.md

@@ -0,0 +1,48 @@
+---
+name: optimize-nurture
+description: Builds a nurture optimization plan with insights, experiments, and remediation tasks.
+usage: /lead-nurture-orchestration:optimize-nurture --window 30d --kpis "activation,pipeline" --segments "enterprise"
+---
+
+# Command: optimize-nurture
+
+## Inputs
+- **window** – reporting period (7d, 14d, 30d, quarter).
+- **kpis** – comma-separated metrics (opens, clicks, conversion, pipeline, velocity, unsub).
+- **segments** – optional audience filters.
+- **experiments** – optional list of running tests to review.
+- **alerts** – optional thresholds for escalations.
+
+### GTM Agents Pattern & Plan Checklist
+> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Optimization usually runs **pipeline** (data → insights → experiments → action plan → governance). If insights and experiment analysis can proceed in parallel, log a **diamond** segment + merge gate.
+- **Plan schema**: Update `.claude/plans/plan-<timestamp>.json` with data sources, query/metric owners, experiment IDs, remediation tasks, risk guardrails, error handling, and success targets (activation %, pipeline lift, unsub ceiling).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` (Serena for pipeline diffs + data pulls, Context7 for platform docs, Sequential Thinking for retrospection, Playwright for QA of revised assets).
+- **Guardrails**: Define retry limit (default 2) for automation fixes; escalation ladder = Nurture Analytics Partner → Marketing Ops Partner → Revenue Operations if alerts breach thresholds.
+- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before sharing to ensure agent coverage + deliverables are complete.
+
+## Workflow
+1. **Data Consolidation** – MAP stats, CRM pipeline, product usage, SDR assist metrics.
+2. **Insight Detection** – highlight stages with drop-offs, fatigue, or high unsub rates.
+3. **Experiment Analysis** – summarize test results, significance, and rollout recommendations.
+4. **Action Plan** – propose new tests, content refresh, audience refinements, or sequencing changes.
+5. **Governance** – log owners, deadlines, and dependencies for each recommendation.
+
+## Outputs
+- Optimization brief (insights, impact, recommended action, owner, due date).
+- Updated experiment tracker with verdicts and next tests.
+- Alert + SLA tracker for segments needing fast intervention.
+- Plan JSON entry stored/updated in `.claude/plans` for auditability.
+
+## Agent/Skill Invocations
+- `nurture-analytics-partner` – leads analysis.
+- `nurture-testing` skill – validates experiment rigor.
+- `lifecycle-cadence` skill – checks pacing vs fatigue thresholds.
+
+## GTM Agents Safeguards
+- **Fallback agents**: record substitutes (e.g., Lifecycle Cadence covering analytics) when primary owners unavailable.
+- **Escalation triggers**: if activation/pipeline KPIs fall below guardrail for two consecutive windows, invoke lifecycle rip-cord and notify Marketing + Sales leadership.
+- **Plan maintenance**: every optimization cycle must append results + changes to the plan JSON and status packets, matching GTM Agents audit expectations.
+
+---

plugin.lock.json

@@ -0,0 +1,77 @@
+{
+  "$schema": "internal://schemas/plugin.lock.v1.json",
+  "pluginId": "gh:gtmagents/gtm-agents:plugins/lead-nurture-orchestration",
+  "normalized": {
+    "repo": null,
+    "ref": "refs/tags/v20251128.0",
+    "commit": "a2d7e6ffc5cdbc6b453bc3329fcf0f65d8895aef",
+    "treeHash": "25205b0733ab463a335e279885714d312849c6b2b466cd1daa9960633a8f9ef4",
+    "generatedAt": "2025-11-28T10:17:11.032598Z",
+    "toolVersion": "publish_plugins.py@0.2.0"
+  },
+  "origin": {
+    "remote": "git@github.com:zhongweili/42plugin-data.git",
+    "branch": "master",
+    "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
+    "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
+  },
+  "manifest": {
+    "name": "lead-nurture-orchestration",
+    "description": "Lifecycle nurture orchestration across segments with automation builds and optimization",
+    "version": "1.0.0"
+  },
+  "content": {
+    "files": [
+      {
+        "path": "README.md",
+        "sha256": "fe3925ca1f6a56ed19e38e1e5f2a0386a1bf93e313ad469243e44c90dcdbf971"
+      },
+      {
+        "path": "agents/nurture-architect.md",
+        "sha256": "ef09e7ed2f289070e5554f887e77bd84316f258291a9b78cd13b0b69d2649bd6"
+      },
+      {
+        "path": "agents/marketing-ops-partner.md",
+        "sha256": "2a4407293a8e435bbcd24ca16a7a03250d4128799717c10fce83071d855d44dc"
+      },
+      {
+        "path": "agents/nurture-analytics-partner.md",
+        "sha256": "34285ad9912dc9f8ae0ca4dffe42e577bc36d8eb6c851f1c4d9bc1095cf76937"
+      },
+      {
+        "path": ".claude-plugin/plugin.json",
+        "sha256": "6988eb7fa1a04e10b84378aff773690f65f02f8f2558b2dc23720bfec5b862d0"
+      },
+      {
+        "path": "commands/optimize-nurture.md",
+        "sha256": "700d04b69f3e030b3f7e504f91c7c2ba397467ff5e93da0d21c57a78daf1d8a3"
+      },
+      {
+        "path": "commands/configure-branches.md",
+        "sha256": "1b8d03af586c7b6d92d10d09ec3a92a1691f388926a84e41fd3705651d123064"
+      },
+      {
+        "path": "commands/design-nurture.md",
+        "sha256": "551ab1e0af40330f90a7ecf5ca2ae99730635e380ec1dee1da0f9a27e187b860"
+      },
+      {
+        "path": "skills/lifecycle-cadence/SKILL.md",
+        "sha256": "3204bea87427eb5c44153f0b473c6977699d79ed3587e688936bf8a7d5aed965"
+      },
+      {
+        "path": "skills/personalization-logic/SKILL.md",
+        "sha256": "3a6174fbd0a66c995848c8aebd00e8c68be9dd0998bf280e06ff30218ff0b991"
+      },
+      {
+        "path": "skills/nurture-testing/SKILL.md",
+        "sha256": "6e025dd795739d6f58cc921bdc6661ec4fd120075c6bc04a312702cce962ab95"
+      }
+    ],
+    "dirSha256": "25205b0733ab463a335e279885714d312849c6b2b466cd1daa9960633a8f9ef4"
+  },
+  "security": {
+    "scannedAt": null,
+    "scannerVersion": null,
+    "flags": []
+  }
+}

skills/lifecycle-cadence/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: lifecycle-cadence
+description: Use when defining nurture pacing, triggers, and suppression logic.
+---
+
+# 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
+1. **Lifecycle Stage Alignment** – ensure cadence matches funnel stage (MQL, SAL, SQL, post-sale).
+2. **Trigger Definition** – entry signals (form fills, intent spikes, product milestones, campaign responses).
+3. **Pacing Rules** – waiting periods, fallback content, stop logic for engagement or conversions.
+4. **Suppression & Priority** – handle conflicting journeys, global caps, sales stages, manual pauses.
+5. **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.
+
+---

skills/nurture-testing/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: nurture-testing
+description: Use when planning, executing, and logging nurture experiments and regression
+  tests.
+---
+
+# 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
+1. **Test Design** – hypothesis, variable, control, variant, KPI, sample size, duration.
+2. **QA Checklist** – links, tokens, segmentation, tracking, device/browser coverage, accessibility.
+3. **Evidence Logging** – screenshots, seed inbox captures, MAP logs, CRM task verification.
+4. **Significance & Rollout** – evaluation method (frequentist/Bayesian), rollout criteria, holdback rules.
+5. **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-logic` and `marketing-ops-partner` to catch edge cases early.
+
+---

skills/personalization-logic/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: personalization-logic
+description: Use when defining dynamic content rules, tokens, and conditional offers
+  inside nurture programs.
+---
+
+# 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
+1. **Segmentation Inputs** – persona, industry, product usage, lifecycle stage, engagement history.
+2. **Content Blocks** – hero, proof, CTA, offer modules with variants per segment.
+3. **Token Management** – define data sources, fallback values, formatting rules.
+4. **Testing Plan** – structure A/B/C tests for personalization depth.
+5. **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` + `design` teams for brand consistency.
+
+---