Menu

Individual skill

lifecycle-journey-map

0upvotes

Builds a customer lifecycle journey map with behavioral entry/exit criteria per stage, one goal and one signal per stage, message briefs, and dead-zone flags. Use when someone asks "map our customer lifecycle", "where are the gaps in our lifecycle emails", "what should we send at each stage", or is aligning a team on lifecycle messaging strategy. Do NOT use to write the actual email sequence - use email-drip-builder for onboarding drips, win-back-campaign for dormant users, or push-notification-copy for push messages; this skill produces the map those campaigns are built on.

skills/lifecycle-journey-map/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Lifecycle Journey Map

A lifecycle map answers one question for every moment a user can be in: what should they feel, know, or do next? Get this right and every downstream campaign has a clear job; skip it and the team ships overlapping messages with no owner, no goal, and no way to know if they worked. The costly mistake this skill prevents is calendar-based messaging - sending on day 7 regardless of what the user actually did.

## Inputs to collect

1. **Product and its first value moment** - the action that proves a user got value (first export, first invoice sent, first report shared). If unknown, propose one and label it a guess to validate against activation data.
2. **Tracked events** - the map can only trigger on events the product already tracks. Get the event list before designing transitions.
3. **Drop-off data per stage transition** - signup→activation rate, activation→habit rate, renewal rate. If unavailable, mark the map "unvalidated" and make pulling this data step 6.
4. **Existing touchpoints** - every email, push, and in-app message currently sent, with its trigger.
5. **Channels available** - email, in-app, push, SMS.

## Operating procedure
Back to top