Initial commit

.claude-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "name": "marketing-automation",
+  "description": "Lifecycle journey orchestration, workflow configuration, and automation governance",
+  "version": "1.0.0",
+  "author": {
+    "name": "GTM Agents",
+    "email": "opensource@intentgpt.ai"
+  },
+  "skills": [
+    "./skills/lifecycle-mapping/SKILL.md",
+    "./skills/workflow-testing/SKILL.md",
+    "./skills/data-governance/SKILL.md"
+  ],
+  "agents": [
+    "./agents/journey-architect.md",
+    "./agents/nurture-operator.md",
+    "./agents/data-orchestrator.md"
+  ],
+  "commands": [
+    "./commands/orchestrate-journey.md",
+    "./commands/configure-workflow.md",
+    "./commands/monitor-automation.md"
+  ]
+}

README.md

@@ -0,0 +1,3 @@
+# marketing-automation
+
+Lifecycle journey orchestration, workflow configuration, and automation governance

agents/data-orchestrator.md

@@ -0,0 +1,27 @@
+---
+name: data-orchestrator
+description: Ensures the right data, consent, and attribution signals power automation workflows end to end.
+model: haiku
+---
+
+# Data Orchestrator Agent
+
+## Responsibilities
+- Map data contracts between product analytics, CDP, CRM, MAP, and warehouse.
+- Define event/field requirements, transformation logic, and SLAs.
+- Monitor data freshness, consent flags, and suppression policies.
+- Coordinate with RevOps/Analytics to govern identities, lead routing, and scoring.
+
+## Operating Flow
+1. **Source Audit** – inventory events, properties, schemas, retention rules.
+2. **Transformation Plan** – define enrichment, normalization, dedupe, and ID resolution steps.
+3. **Delivery Blueprint** – specify reverse ETL jobs, API/webhook payloads, failsafes.
+4. **Compliance Check** – consent management, regional policies, kill switches.
+5. **Monitoring** – dashboards + alerts for data delays, drift, schema changes.
+
+## Outputs
+- Data enablement spec for each journey (fields, sources, freshness, owners).
+- Incident response runbook for data failures.
+- Change log documenting schema/version updates.
+
+---

agents/journey-architect.md

@@ -0,0 +1,27 @@
+---
+name: journey-architect
+description: Designs multi-channel automation programs spanning email, in-app, SMS, and webhooks.
+model: sonnet
+---
+
+# Journey Architect Agent
+
+## Responsibilities
+- Translate lifecycle goals into audience segmentation, trigger logic, and branching.
+- Map orchestration patterns that reuse modular steps and integrate other GTM systems.
+- Coordinate with campaign, ops, product, and legal teams to align SLAs and compliance.
+- Maintain documentation and measurement frameworks for every automation track.
+
+## Workflow
+1. **Brief Intake** – capture goal, personas, channels, success metrics.
+2. **Data Audit** – inventory events, fields, consent, suppression logic.
+3. **Journey Blueprint** – draft entry criteria, steps, waits, decision branches, fallbacks.
+4. **Resource Plan** – identify creative assets, API/webhook calls, engineering dependencies.
+5. **QA & Measurement** – define test plan, launch gates, dashboards, and experiment ideas.
+
+## Outputs
+- Journey diagram + configuration spec (JSON/YAML) for MA platforms.
+- SLA + compliance checklist per channel and region.
+- Experiment backlog and change-log for future iterations.
+
+---

agents/nurture-operator.md

@@ -0,0 +1,27 @@
+---
+name: nurture-operator
+description: Configures automation workflows inside MAP/CRM tools, ensuring assets, personalization, and QA are production-ready.
+model: haiku
+---
+
+# Nurture Operator Agent
+
+## Responsibilities
+- Build automation flows (HubSpot, Marketo, Iterable, Braze, Customer.io) per blueprint.
+- Configure personalization tokens, dynamic content blocks, and conditional branches.
+- Set up wait timers, throttling, re-entry logic, and suppression lists.
+- Run QA (seed list tests, device/browser checks, accessibility, compliance).
+
+## Implementation Flow
+1. **Blueprint Intake** – confirm triggers, branching, assets, and SLAs.
+2. **Asset Wiring** – attach emails/SMS/push, configure tracking, set UTMs.
+3. **Logic Build** – implement splits, scoring rules, webhook/API steps.
+4. **QA & Approvals** – run multi-channel tests, gather stakeholder approvals, document evidence.
+5. **Launch + Monitoring** – schedule go-live, set alerting, watch logs and performance.
+
+## Deliverables
+- Workflow configuration notes + screenshots.
+- QA checklist results and sign-offs.
+- Monitoring dashboard links and alert thresholds.
+
+---

commands/configure-workflow.md

@@ -0,0 +1,32 @@
+---
+name: configure-workflow
+description: Produces implementation instructions for building the automation inside MAP/CRM tools, including QA steps.
+usage: /marketing-automation:configure-workflow --journey onboarding --platform hubspot
+---
+
+# Command: configure-workflow
+
+## Inputs
+- **journey** – reference journey ID or description.
+- **platform** – automation platform (hubspot, marketo, braze, iterable, customerio, etc.).
+- **assets** – optional list of email/SMS/push templates to wire.
+- **qa_mode** – true/false to include full regression suite.
+
+## Workflow
+1. **Blueprint Sync** – pull orchestration diagram + requirements.
+2. **Platform Mapping** – translate logic into platform-specific objects (smart lists, workflows, campaigns, journeys).
+3. **Configuration Steps** – detailed instructions for triggers, branches, waits, webhook/API calls, personalization tokens.
+4. **QA Matrix** – build test plan (seed recipients, device/browser, fallback paths, compliance checkpoints).
+5. **Launch Checklist** – approvals, scheduling, monitoring, rollback plan.
+
+## Outputs
+- Step-by-step build guide with screenshots/snippets.
+- QA checklist and evidence log template.
+- Launch readiness form (owners, go-live date, monitoring links).
+
+## Agent/Skill Invocations
+- `nurture-operator` – executes build tasks.
+- `workflow-testing` skill – ensures QA rigor.
+- `data-orchestrator` – validates data/suppression wiring.
+
+---

commands/monitor-automation.md

@@ -0,0 +1,32 @@
+---
+name: monitor-automation
+description: Generates reporting + alerting plan to track automation health, experiment performance, and SLA compliance.
+usage: /marketing-automation:monitor-automation --journey onboarding --window 14d --metrics "activation,retention"
+---
+
+# Command: monitor-automation
+
+## Inputs
+- **journey** – automation identifier.
+- **window** – reporting cadence (7d, 14d, 30d, rolling).
+- **metrics** – comma-separated KPIs (activation, retention, revenue, NPS, pipeline).
+- **experiments** – optional list of A/B/C tests to track.
+
+## Workflow
+1. **KPI Mapping** – align goals to metrics, data sources, attribution windows.
+2. **Instrumentation Audit** – confirm events/fields exist, dashboards, alerts, and experiment IDs.
+3. **Insight Generation** – highlight drop-offs, bottlenecks, fatigue, list growth, deliverability, suppression trends.
+4. **Action Plan** – recommend experiments, content refresh, cadence tweaks, or routing updates.
+5. **Governance** – log changes in journey changelog, assign owners, set follow-up dates.
+
+## Outputs
+- Dashboard spec (Looker/Tableau/GDS) plus SQL snippets.
+- Weekly digest template with insights + recommended actions.
+- Alert configuration guide (Amplitude/Braze/Husky) for SLA breaches.
+
+## Agent/Skill Invocations
+- `data-orchestrator` – ensures accurate instrumentation.
+- `workflow-testing` skill – sets up regression tests/alerts.
+- `lifecycle-mapping` skill – contextualizes metrics by stage.
+
+---

commands/orchestrate-journey.md

@@ -0,0 +1,33 @@
+---
+name: orchestrate-journey
+description: Generates an end-to-end automation blueprint with trigger logic, steps, and measurement.
+usage: /marketing-automation:orchestrate-journey --goal onboarding --persona founders --channels "email,SMS,in-app"
+---
+
+# Command: orchestrate-journey
+
+## Inputs
+- **goal** – lifecycle stage or desired outcome (onboarding, expansion, renewal, retention).
+- **persona** – audience segment with shared needs.
+- **channels** – comma-delimited list of active channels.
+- **length** – optional number of total steps.
+- **constraints** – legal, compliance, or SLA notes.
+
+## Workflow
+1. **Brief Parsing** – gather goals, KPIs, constraints.
+2. **Trigger & Entry Mapping** – define events, qualification, suppression, re-entry rules.
+3. **Journey Design** – outline each step with channel, content objective, personalization, fallback logic.
+4. **Data/Asset Plan** – list required fields, APIs, assets, owners, and deadlines.
+5. **Testing & Measurement** – propose QA plan, launch gates, dashboards, experiments.
+
+## Outputs
+- Journey diagram (mermaid) with branching logic.
+- Configuration spec (JSON/YAML) for MAP/CRM systems.
+- Measurement plan with KPIs, alerts, and experiment backlog.
+
+## Agent/Skill Invocations
+- `journey-architect` – drives strategy and blueprint.
+- `lifecycle-mapping` skill – enforces best-practice cadence and segmentation.
+- `data-orchestrator` – confirms data requirements.
+
+---

plugin.lock.json

@@ -0,0 +1,77 @@
+{
+  "$schema": "internal://schemas/plugin.lock.v1.json",
+  "pluginId": "gh:gtmagents/gtm-agents:plugins/marketing-automation",
+  "normalized": {
+    "repo": null,
+    "ref": "refs/tags/v20251128.0",
+    "commit": "21e04f369e3ac47063b9693008ad189ec77f2db9",
+    "treeHash": "7f398218b59ef8838750337d3ba4f1100ff2d7f8ec423344eba0d2665a60cf71",
+    "generatedAt": "2025-11-28T10:17:08.974305Z",
+    "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": "marketing-automation",
+    "description": "Lifecycle journey orchestration, workflow configuration, and automation governance",
+    "version": "1.0.0"
+  },
+  "content": {
+    "files": [
+      {
+        "path": "README.md",
+        "sha256": "13c936f39920d56cab1f1fd3896303203a70b7db38a4fa90d02ee575432586ab"
+      },
+      {
+        "path": "agents/data-orchestrator.md",
+        "sha256": "ae49f9e8268c91ecfd1c3bde788499ee4a60385acef80a76998bd14a13497f9e"
+      },
+      {
+        "path": "agents/nurture-operator.md",
+        "sha256": "67ccfbc27621696cdcad5e2e9168ec5ab30586581e3e640db88f46e4b3c7b7ea"
+      },
+      {
+        "path": "agents/journey-architect.md",
+        "sha256": "427f3ec8a52247fed00fab9799eac2316db4a5f723f001d1c14b58dd1a8e7162"
+      },
+      {
+        "path": ".claude-plugin/plugin.json",
+        "sha256": "fb52e213a01bf75e0f038b23ec729b7844e3e69f9714543d2523a204d84dd3e9"
+      },
+      {
+        "path": "commands/monitor-automation.md",
+        "sha256": "8039eb31a15840175da56e0bf90dfd03f8e0458434e907a7de7d6569b4ebf955"
+      },
+      {
+        "path": "commands/configure-workflow.md",
+        "sha256": "04794c9b4961969a71634c795503964c3fc79b6c51dabdb3e2f10b16449da938"
+      },
+      {
+        "path": "commands/orchestrate-journey.md",
+        "sha256": "1d435fd09a5ef51b52d315e669efbe75d5102eca87accac946eb2461775751e3"
+      },
+      {
+        "path": "skills/workflow-testing/SKILL.md",
+        "sha256": "db6e9ded15543bf2b17a837a6ca6ad74bad1e6a7668f3951d09c42246d4d1b1a"
+      },
+      {
+        "path": "skills/data-governance/SKILL.md",
+        "sha256": "48a0783cc7e379bd22da218ea3560fa47742d4056969af0b64be2e5762e5ab3e"
+      },
+      {
+        "path": "skills/lifecycle-mapping/SKILL.md",
+        "sha256": "413bdbfbc0c1c034205eb708ca3799f27e80953cebd47b6d30e86d51399d1cee"
+      }
+    ],
+    "dirSha256": "7f398218b59ef8838750337d3ba4f1100ff2d7f8ec423344eba0d2665a60cf71"
+  },
+  "security": {
+    "scannedAt": null,
+    "scannerVersion": null,
+    "flags": []
+  }
+}

skills/data-governance/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: data-governance
+description: Use when defining data contracts, consent policies, and monitoring for
+  automation programs.
+---
+
+# Automation Data Governance Skill
+
+## When to Use
+- Launching new journeys requiring cross-system data sharing.
+- Auditing consent/suppression logic across email/SMS/in-app.
+- Investigating data quality incidents impacting automation.
+
+## Framework
+1. **Data Contracts** – document required fields/events, owners, freshness SLAs, fallback behavior.
+2. **Consent & Compliance** – track opt-in types, regional consent, TTL, audit trails.
+3. **Identity Resolution** – ensure consistent IDs across product, CRM, MAP, CDP.
+4. **Monitoring** – dashboards/alerts for data latency, schema changes, null spikes.
+5. **Change Management** – versioning, rollback, and communication paths.
+
+## Templates
+- Data requirements matrix (journey → fields/events → source → owner → SLA).
+- Consent policy doc (channel, region, legal basis, suppression rules).
+- Incident log + RCA template.
+
+## Tips
+- Set automated kill switches when critical fields are stale or missing.
+- Collaborate with security/legal on retention + privacy impact assessments.
+- Align governance cadences with quarterly automation retros.
+
+---

skills/lifecycle-mapping/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: lifecycle-mapping
+description: Use when designing automation programs aligned to lifecycle stages, SLAs,
+  and GTM objectives.
+---
+
+# Lifecycle Mapping Frameworks Skill
+
+## When to Use
+- Blueprinting onboarding, expansion, renewal, or churn-prevention journeys.
+- Aligning automation programs with account stages, ICP tiers, or health scores.
+- Auditing existing programs for gaps or over-saturation.
+
+## Framework
+1. **Stage Definition** – awareness, activation, adoption, expansion, advocacy (customize per business).
+2. **Signal Library** – activation events, product usage milestones, score thresholds, purchase behaviors.
+3. **Touch Architecture** – how many touches per stage, channel mix, personal vs automated.
+4. **SLA Matrix** – entry/exit criteria, owner, response time, success metrics.
+5. **Experiment Layer** – embed test slots to iterate hooks, cadences, or offers per stage.
+
+## Templates
+- Lifecycle heat map (stage vs metric vs automation coverage).
+- SLA worksheet (stage, trigger, owner, time-to-response, fallback).
+- Journey backlog board (ideas, prioritized, building, live, measuring).
+- **GTM Agents Campaign Planning Checklist** – captures marketing director playbook @puerto/README.md#183-212.
+- **KPI Guardrails Sheet** – track reach, engagement, SQL impact, CAC payback with min/max thresholds.
+- **Status Packet Template** – weekly single-slide update mirroring GTM Agents project-manager format @puerto/TEAM-STRUCTURE.md#193-204.
+
+## Tips
+- Limit simultaneous journeys per contact; define prioritization rules.
+- Include manual checkpoints (CSM/AE) for high-touch segments.
+- Document every assumption so experiments can deliberately challenge them.
+- Lock KPIs before build starts and refuse scope creep until metrics + owners are confirmed.
+- Borrow GTM Agents's cadence: **Plan → Build → QA → Launch → Inspect** so reporting lines know when to approve or intervene.
+- Pair every automation change with a "rip-cord" procedure the Sales Director or Ops Lead can trigger if leading indicators degrade.
+
+## GTM Agents Campaign Blueprint (Adopted)
+Use this five-stage blueprint when large GTM initiatives require orchestration across demand gen, lifecycle, and RevOps teams:
+
+1. **Stage 1 – Briefing & Alignment**
+   - Confirm objective, ICP, offer, timeline, and budget.
+   - Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.
+2. **Stage 2 – Architecture**
+   - Map lifecycle stages to channels + automations.
+   - Define entry/exit criteria, personalization logic, and compliance constraints.
+   - Assign data availability checks (Serena) + documentation pulls (Context7) if needed.
+3. **Stage 3 – Build & QA**
+   - Break work into swimlanes (journey build, content, data, QA) and track in backlog.
+   - Require Playwright or similar browser QA for every externally facing experience.
+4. **Stage 4 – Launch & Monitor**
+   - Set Day 0/Day 7 KPI guardrails (e.g., form conversion ≥ 4%, unsubscribe ≤ 0.4%).
+   - Route anomalies to the Operations Lead with a rollback procedure.
+5. **Stage 5 – Inspect & Iterate**
+   - Use Sequential Thinking to run structured retros (what worked, what failed, hypotheses for next wave).
+   - Feed learnings back into lifecycle heat map + SLA matrix.
+
+## Status Reporting Template
+```
+Campaign: <Name>
+Week Ending: <Date>
+
+1. Highlights (wins, blockers, escalations)
+2. KPI Snapshot (target vs actual vs guardrail)
+3. Journey Coverage (stage, channel, live %)
+4. Next 5 Actions (owner, due date)
+5. Risks & Decisions Needed (include GTM Agents-style RAG)
+```
+
+Use this template to sync with Sales Director, Partnership Manager, and Project Manager counterparts each week.
+
+---

skills/workflow-testing/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: workflow-testing
+description: Use when validating automation builds before launch or after significant
+  changes.
+---
+
+# Workflow Testing & QA Skill
+
+## When to Use
+- Any new automation or major revision prior to go-live.
+- Regression testing after data, asset, or logic changes.
+- Investigating deliverability, conversion, or routing anomalies.
+
+## Framework
+1. **Unit Tests** – confirm each branch, wait step, and action path with seed contacts.
+2. **Integration Tests** – verify webhook/API calls, CRM updates, enrichment, scoring.
+3. **Content QA** – links, tracking, personalization tokens, accessibility, localization.
+4. **Compliance** – consent, suppression, GDPR/CASL/CCPA rules, regional requirements.
+5. **Performance** – throttle checks, concurrency, error handling, failover.
+
+## Checklist
+- Seed list matrix (personas, stages, regions, consent flags).
+- Device/browser testing for email/SMS/push rendering.
+- Logging + alerting validation.
+- Rollback and kill switches documented.
+
+## Templates
+- QA evidence log (screenshot, recipient, status, owner).
+- Incident runbook for automation failures.
+- Release checklist referencing stakeholders.
+
+## Tips
+- Automate regression tests via APIs or synthetic users.
+- Store test data separately and purge regularly to avoid reporting noise.
+- Use feature flags to stage rollouts before full scale.
+
+---