Lifecycle Metrics

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 npx skillpacks install <pack> from the project shell, 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.

Process

0. Product-Path Scope Resolution

Resolve research scope by product path before using code or app structure as a hint:

1. If $ARGUMENTS names a non-archived research/{slug}/ directory or a product-path ID whose scope_path points there, use that path. Treat {slug} as the product/app name, not the ICP, audience, or segment label.
2. If $ARGUMENTS names only research/_archive/{slug}/ or a manifest entry with status: archived or legacy status: abandoned, stop and warn that the path is archived; do not write or update scoped outputs there.
3. Read research/.progress.yaml when present. Normalize legacy active_path to active_paths on read and write back active_paths on manifest updates. Treat legacy abandoned as archived; exclude archived, abandoned, deferred, revisit_candidate, promoted, and any scope_path under research/_archive/ from active target selection.
4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
5. If no active manifest target exists, list non-archived product directories under research/, excluding research/_archive/ and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
6. If no product directories exist, use flat research/ single-product mode.
7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing research/{slug}/ product path when code clearly exposes an app, but do not require code or monorepo detection before using research/{slug}/.

When product path {slug} is active, read and write research under research/{slug}/, specs under specs/{slug}/, and treat top-level research/*.md files as flat-mode documents or cross-path summaries.

1. Resolve product-path scope using research/{slug}/ when applicable.
2. Read research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading; treat legacy abandoned as archived and exclude archived/deferred/revisit/promoted paths plus research/_archive/ scopes from active target selection. Scope lifecycle metrics to the active product path by default.
3. Require research/journey-map.md; load any focused lifecycle maps that exist.
4. Load ICP, customer feedback, existing metrics, specs, README, and current analytics/instrumentation code when present.
5. 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.
6. Present the lifecycle measurement model before writing.
7. Write research/lifecycle-metrics.md and research/lifecycle-metrics-interview.md in flat mode, or research/{slug}/lifecycle-metrics.md and research/{slug}/lifecycle-metrics-interview.md when product-path scope is active, 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 via the packaged convention resolver; output path is 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.

Default Shipping Contract

Follow the shared shipping contract convention in CLAUDE.md.