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.
Retention Map
Invoke as $retention-map.
Map why customers return, what predicts churn, and how the product recovers at-risk users.
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 the retention map to the active product path by default.
- Require
research/journey-map.md; if missing, recommend $journey-map.
- Load journey, onboarding, conversion, transaction, metrics, customer feedback, specs, and product evidence when present.
- Interview and recommend around: repeat-use job, natural frequency, core habit/workflow loop, lifecycle messages, saved state, collaboration, renewal moments, churn triggers, downgrade/cancel paths, winback, support recovery, and leading indicators.
- Present the retention model and risk assumptions before writing.
- Write
research/retention-map.md and research/retention-map-interview.md after validation.
Output Shape
# Retention Map
> Based on: research/journey-map.md
> Date: YYYY-MM-DD
## Summary
## Repeat-Use Loop
## Lifecycle Triggers
## Healthy Usage Signals
## Churn Triggers
## Recovery And Winback
## Product Gaps
## 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/retention-map-{topic}.html.
Constraints
- Do not force habit-loop language onto naturally infrequent or transactional products; document the natural return trigger instead.
- End with
## Next Steps, preferring $expansion-map, $lifecycle-metrics, $hook-model, $customer-feedback, or $cohort-review as context dictates.
1---2name: retention-map-43description: Plan repeat-use loops, lifecycle triggers, churn risks, recovery paths, and retention signals4---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# Retention Map
11
12Invoke as `$retention-map`.
13
14Map why customers return, what predicts churn, and how the product recovers at-risk users.
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 the retention map to the active product path by default.
203. Require `research/journey-map.md`; if missing, recommend `$journey-map`.
214. Load journey, onboarding, conversion, transaction, metrics, customer feedback, specs, and product evidence when present.
225. Interview and recommend around: repeat-use job, natural frequency, core habit/workflow loop, lifecycle messages, saved state, collaboration, renewal moments, churn triggers, downgrade/cancel paths, winback, support recovery, and leading indicators.
236. Present the retention model and risk assumptions before writing.
247. Write `research/retention-map.md` and `research/retention-map-interview.md` after validation.
25
26## Output Shape
27
28```markdown
29# Retention Map
30
31> Based on: research/journey-map.md
32> Date: YYYY-MM-DD
33
34## Summary
35## Repeat-Use Loop
36## Lifecycle Triggers
37## Healthy Usage Signals
38## Churn Triggers
39## Recovery And Winback
40## Product Gaps
41## Next Steps
42```
43
44## Alignment Page
45
46When 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/retention-map-{topic}.html`.
47
48## Constraints
49
50- Do not force habit-loop language onto naturally infrequent or transactional products; document the natural return trigger instead.
51- End with `## Next Steps`, preferring `$expansion-map`, `$lifecycle-metrics`, `$hook-model`, `$customer-feedback`, or `$cohort-review` as context dictates.
GeorgeQLe