lifecycle-mapping — Claude Code skill: what it does, how to install
lifecycle-mapping splits lifecycle automation into stages, signals, touches and SLA rules, with room for tests. Useful when onboarding or retention programs need one shared scheme.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a claude-codeWhat lifecycle-mapping does
The skill hands over a five-step frame. You define stages from awareness to advocacy, list the signals that move an account between them, decide how many touches each stage gets and on which channel, then write an SLA matrix with entry and exit rules. A fifth layer reserves space for tests so hooks and cadences can be swapped per stage.
Templates ship with it: a heat map of stages against metrics and automation coverage, an SLA worksheet, a backlog board for journeys, a campaign planning checklist and a sheet of KPI guardrails. Larger initiatives follow a five-stage blueprint that runs from briefing to retro. Every externally facing experience in that blueprint needs browser QA through Playwright or a similar tool, otherwise the launch step stays uncovered.
Two habits keep a program from collapsing. Cap how many journeys one contact sits in, and lock the KPIs before the build starts so scope does not creep. The skill also asks for a rip-cord procedure that a sales director or ops lead can pull when leading indicators fall.
What it helps with
- map an onboarding flow to lifecycle stages and channels
- write SLA rules with owners and response times
- audit running automations for gaps and overload
- lock KPI guardrails before a campaign goes live
- produce a one-slide weekly status for a campaign
Example prompts for the agent
- Map our onboarding flow to lifecycle stages and flag where touches are missing
- Build the SLA matrix: stage, trigger, owner, response time and fallback
- Audit our running journeys for over-saturation per contact
How to install lifecycle-mapping
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a claude-code2Manually: put the files in place
~/.claude/skills/lifecycle-mapping/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lifecycle-mapping/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a codex2Manually: put the files in place
.agents/skills/lifecycle-mapping/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a cursor2Manually: put the files in place
.cursor/skills/lifecycle-mapping/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/marketing-automation/skills/lifecycle-mapping2Manually: put the files in place
.github/skills/lifecycle-mapping/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/marketing-automation/skills/lifecycle-mappingManually: put the files in place
.devin/skills/lifecycle-mapping/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about lifecycle-mapping
How do I install lifecycle-mapping in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a claude-code. The skill lands at ~/.claude/skills/lifecycle-mapping/SKILL.md.
What does lifecycle-mapping do?
It helps design automation around lifecycle stages: which signals move an account, how touches spread across channels, an SLA matrix and slots for experiments. Each block comes with a template, from a heat map to a backlog board.
What does the campaign blueprint need before launch?
Browser QA through Playwright or a similar tool for every externally facing experience, plus agreed KPIs and owners. Anomalies at day 0 and day 7 go to the operations lead together with a rollback procedure.
Source text
SKILL.md · Apache-2.0
--- 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. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents