lifecycle-mapping
Use when designing automation programs aligned to lifecycle stages, SLAs, and GTM objectives.
What this skill does
# 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. ---
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.