Initial commit

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.
+
+---