lifecycle-map

Lifecycle Map — Event → Stage Mapping

Turn the event inventory from lifecycle-connect into a stage map and funnel skeleton. This is what makes journey eligibility computable.

When NOT to use this

• No DQS or event inventory exists yet — there is nothing to map; run lifecycle-connect first.
• The question is whether a specific automation should be kept, changed, or killed — that's lifecycle-audit (structural review) or lifecycle-results (outcome-based), not this skill.
• The need is an audience query for an already-designed journey — that's lifecycle-audience. This skill produces the stage map and funnel skeleton, never a runnable query.

Procedure

1. If knowledge/brands/<brand>.md has verticals set: tag every event to a vertical via event_prefix match first — mechanical name-prefix matching, done before any stage classification. This determines which industry playbook's funnel table and "Event expectations" apply to that event in step 1. An event matching no vertical's prefix falls back to the primary industry, flagged unclassified-vertical — batch it into the same question as unmappable events (step 3).
2. First, check for a prior pass: if output/<project>/event-analysis.json exists (written when lifecycle-connect spawned event-analyst for a 50+ event inventory earlier in this same run), its Mapped/Assumed/Unmapped classification is a draft, not a discard-and-redo — confirm or override it below rather than reclassifying every event from zero. Two independent classification passes over the same event risk landing on two different stages for it — treating the first pass as the starting point removes that risk instead of hoping both agree. Absent the file (inventories under 50 events, classified inline by lifecycle-connect itself, or no prior connect run), load the mapping sources fresh, in lookup order:
   • ${CLAUDE_PLUGIN_ROOT}/knowledge/event-taxonomy/ga4-recommended-events.md (exact + alias lookup)
   • the active industry playbook's funnel table (the event's own vertical's playbook, for multi-vertical brands)
   • ${CLAUDE_PLUGIN_ROOT}/knowledge/event-taxonomy/stage-mapping-rules.md (heuristics for unknowns — apply its rules 1→5 in order)
3. Classify every event from the inventory. Track WHICH rule classified each one.
4. Batch unmappable events into a single question to the user (max 10, best-guess pre-filled). Continue with what is mapped; mark dependent outputs provisional.
5. Build the funnel skeleton: order the mapped events along the industry playbook's canonical funnel (one skeleton per vertical, for multi-vertical brands); note observed drop-off between steps if T1 volumes exist — and flag, don't silently build past, any step whose volume exceeds the previous step's. An inverted funnel means a mapping error or a data-integrity problem, not real user behavior; report it as a finding rather than presenting the funnel as if the numbers were trustworthy.