Pack Availability Guard
Before telling the user to run a skill from another project-local pack, check .agents/project.json.enabled_packs. If the target pack is not enabled, recommend /pack install <pack> instead of the target skill.
Lifecycle Metrics
Define measurable signals for each lifecycle stage. This complements /metrics: use this skill for stage instrumentation and handoff clarity, then use /metrics for the broader success framework, targets, and business metrics.
Workflow
- Resolve app scope using
research/{app}/ when applicable.
- Require
research/journey-map.md; load any focused lifecycle maps that exist.
- Load ICP, customer feedback, existing metrics, specs, README, and current analytics/instrumentation code when present.
- Interview and recommend around: stage entry/exit events, activation, conversion, payment success/failure, retention health, churn risk, expansion readiness, evidence quality, measurement owner, and instrumentation gaps.
- Present the lifecycle measurement model before writing.
- Write
research/lifecycle-metrics.md and research/lifecycle-metrics-interview.md after validation.
Output Shape
# Lifecycle Metrics
> Based on: research/journey-map.md[, lifecycle stage maps]
> Date: YYYY-MM-DD
## Summary
## Stage Metrics
## Event And Property Inventory
## Instrumentation Gaps
## Baselines And Targets To Define In Metrics
## Record-Todo Candidates
## Next Steps
Alignment Page
Follow the shared Alignment Page convention in CLAUDE.md. Output: alignment/lifecycle-metrics-{topic}.html.
Constraints
- Do not duplicate the full
/metrics framework; link unresolved targets to /metrics.
- Put future, non-blocking measurements in
tasks/record-todo.md when the skill is executed.
- End with
## Next Steps, preferring /metrics, /roadmap, /exec, or /cohort-review as context dictates.
1---2name: lifecycle-metrics-63description: Define stage metrics, instrumentation needs, and evidence gaps across onboarding, conversion, transaction, retention, and expansion4---5
6## Pack Availability Guard
7
8Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `/pack install <pack>` instead of the target skill.
9
10# Lifecycle Metrics
11
12
13
14Define measurable signals for each lifecycle stage. This complements `/metrics`: use this skill for stage instrumentation and handoff clarity, then use `/metrics` for the broader success framework, targets, and business metrics.
15
16## Workflow
17
181. Resolve app scope using `research/{app}/` when applicable.
192. Require `research/journey-map.md`; load any focused lifecycle maps that exist.
203. Load ICP, customer feedback, existing metrics, specs, README, and current analytics/instrumentation code when present.
214. Interview and recommend around: stage entry/exit events, activation, conversion, payment success/failure, retention health, churn risk, expansion readiness, evidence quality, measurement owner, and instrumentation gaps.
225. Present the lifecycle measurement model before writing.
236. Write `research/lifecycle-metrics.md` and `research/lifecycle-metrics-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Lifecycle Metrics
29
30> Based on: research/journey-map.md[, lifecycle stage maps]
31> Date: YYYY-MM-DD
32
33## Summary
34## Stage Metrics
35## Event And Property Inventory
36## Instrumentation Gaps
37## Baselines And Targets To Define In Metrics
38## Record-Todo Candidates
39## Next Steps
40```
41
42## Alignment Page
43
44Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/lifecycle-metrics-{topic}.html`.
45
46## Constraints
47
48- Do not duplicate the full `/metrics` framework; link unresolved targets to `/metrics`.
49- Put future, non-blocking measurements in `tasks/record-todo.md` when the skill is executed.
50- End with `## Next Steps`, preferring `/metrics`, `/roadmap`, `/exec`, or `/cohort-review` as context dictates.
GeorgeQLe