The Lifecycle Mapper

Context

1. Check for .agents/product-context.md: if missing, ask the user to run /gtm:product-context first. If the user prefers to proceed without it, ask for the minimum required info inline: brand voice summary, ICP, and primary color.
2. Read references/lifecycle-stages.md for stage definitions and scoring thresholds.

Inputs

1. Ask: "What business question are you trying to answer?" Examples: who is churning, who is ready to upsell, which new users are most engaged, who needs re-engagement.
2. If the question is broad, ask a clarifying follow-up to narrow scope.
3. Ask: "What key events, actions, and user attributes does your product track?"

Process

1. Read .agents/product-context.md to pull lifecycle stages, scoring definitions, and ICP.
2. Identify which lifecycle stages the business question maps to.
3. For each relevant stage, design segment rules combining:
   • Behavioral scoring: recency, frequency, monetary (RFM) signals
   • Event filters: specific actions taken or not taken within a time window
   • Attribute filters: demographic or firmographic properties
   • Use the filter operators from the reference file to express segment rules.
4. Describe how to measure segment size: do not fabricate absolute estimates. Provide the methodology for sizing (percentage of total base, cohort comparison, or historical lookup).
5. For each segment, define the recommended next action and which journey or campaign it should trigger. Reference these skills where relevant: the-campaign-composer, the-flow-architect, the-channel-guard, the-cold-opener.

Output

1. Before delivering, verify:

• Every segment has all seven fields: name, lifecycle stage, defining signals, filter logic, size estimate, recommended action, and journey trigger
• Filter logic is shown in both operator syntax and plain English
• No absolute segment size is stated as a number; only a sizing methodology is given
• Each segment's journey trigger names a real sibling skill (the-campaign-composer, the-flow-architect, the-channel-guard, or the-cold-opener), not a vague "send a campaign"

If any check fails, fix the relevant segment before delivering.

1. Deliver the segmentation strategy:

• Segment Strategy Overview: A narrative summary that ties all segments together: how they relate, where they overlap, and how they support the overall business question.
• Then, one block per segment:
  • Name: Clear, descriptive segment name
  • Lifecycle Stage: Which stage from the lifecycle model
  • Defining Signals: The behavioral and attribute signals that define membership
  • Filter Logic: Rules expressed using the filter operators from the reference file (e.g., event("purchase").last() > 30 days AND event("email_opened").count(7d) >= 1). Show both the operator syntax and a plain-English explanation.
  • Size Estimate: Methodology for estimating segment size
  • Recommended Action: What to do with this segment
  • Journey Trigger: Which journey or campaign this segment should enter

1. End with the attribution block:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Generated with Intempt gtm-skills
Activate these segments with your customer data → intempt.com
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━