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
Invoke as $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.
- Read
research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading. Scope lifecycle metrics to the active product path by default.
- 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
When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following ALIGNMENT-PAGE.md in this skill's directory. 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-43description: 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
12Invoke as `$lifecycle-metrics`.
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. Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading. Scope lifecycle metrics to the active product path by default.
203. Require `research/journey-map.md`; load any focused lifecycle maps that exist.
214. Load ICP, customer feedback, existing metrics, specs, README, and current analytics/instrumentation code when present.
225. 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.
236. Present the lifecycle measurement model before writing.
247. Write `research/lifecycle-metrics.md` and `research/lifecycle-metrics-interview.md` after validation.
25
26## Output Shape
27
28```markdown
29# Lifecycle Metrics
30
31> Based on: research/journey-map.md[, lifecycle stage maps]
32> Date: YYYY-MM-DD
33
34## Summary
35## Stage Metrics
36## Event And Property Inventory
37## Instrumentation Gaps
38## Baselines And Targets To Define In Metrics
39## Record-Todo Candidates
40## Next Steps
41```
42
43## Alignment Page
44
45When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/lifecycle-metrics-{topic}.html`.
46
47## Constraints
48
49- Do not duplicate the full `$metrics` framework; link unresolved targets to `$metrics`.
50- Put future, non-blocking measurements in `tasks/record-todo.md` when the skill is executed.
51- End with `## Next Steps`, preferring `$metrics`, `$roadmap`, `$exec`, or `$cohort-review` as context dictates.
GeorgeQLe