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
Map why customers return, what predicts churn, and how the product recovers at-risk users.
Workflow
- Resolve app scope using
research/{app}/ when applicable.
- 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
Follow the shared Alignment Page convention in CLAUDE.md. 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-63description: 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
12
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. Require `research/journey-map.md`; if missing, recommend `/journey-map`.
203. Load journey, onboarding, conversion, transaction, metrics, customer feedback, specs, and product evidence when present.
214. 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.
225. Present the retention model and risk assumptions before writing.
236. Write `research/retention-map.md` and `research/retention-map-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Retention Map
29
30> Based on: research/journey-map.md
31> Date: YYYY-MM-DD
32
33## Summary
34## Repeat-Use Loop
35## Lifecycle Triggers
36## Healthy Usage Signals
37## Churn Triggers
38## Recovery And Winback
39## Product Gaps
40## Next Steps
41```
42
43## Alignment Page
44
45Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/retention-map-{topic}.html`.
46
47## Constraints
48
49- Do not force habit-loop language onto naturally infrequent or transactional products; document the natural return trigger instead.
50- End with `## Next Steps`, preferring `/expansion-map`, `/lifecycle-metrics`, `/hook-model`, `/customer-feedback`, or `/cohort-review` as context dictates.
GeorgeQLe