Initial commit

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