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.
Expansion Map
Invoke as $expansion-map.
Map how retained customers grow into larger accounts, higher usage, referrals, or advocacy.
Workflow
- Resolve app scope using
research/{app}/ when applicable.
- Require
research/journey-map.md; if missing, recommend $journey-map.
- Load journey, retention, monetization, GTM, enterprise ICP, metrics, customer feedback, and specs when present.
- Interview and recommend around: expansion trigger, added seats/users, usage expansion, tier upgrades, team rollout, integrations, procurement renewal, referrals, reviews, advocacy, and account-health thresholds.
- Present the expansion model before writing.
- Write
research/expansion-map.md and research/expansion-map-interview.md after validation.
Output Shape
# Expansion Map
> Based on: research/journey-map.md[, research/retention-map.md]
> Date: YYYY-MM-DD
## Summary
## Expansion Triggers
## Upgrade And Seat Growth Paths
## Team Or Account Rollout
## Referral And Advocacy Paths
## Risks And Constraints
## Product Gaps
## Next Steps
Alignment Page
Follow the shared Alignment Page convention in CLAUDE.md. Output: alignment/expansion-map-{topic}.html.
Constraints
- Separate genuine expansion from ordinary retention.
- For enterprise products, identify champion, buyer, admin, security, and procurement roles when relevant.
- End with
## Next Steps, preferring $lifecycle-metrics, $monetization, $growth-model, $gtm as context dictates.
1---2name: expansion-map-33description: Plan account expansion, upgrades, seat growth, referrals, advocacy, and land-and-expand paths4---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# Expansion Map
11
12Invoke as `$expansion-map`.
13
14Map how retained customers grow into larger accounts, higher usage, referrals, or advocacy.
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, retention, monetization, GTM, enterprise ICP, metrics, customer feedback, and specs when present.
214. Interview and recommend around: expansion trigger, added seats/users, usage expansion, tier upgrades, team rollout, integrations, procurement renewal, referrals, reviews, advocacy, and account-health thresholds.
225. Present the expansion model before writing.
236. Write `research/expansion-map.md` and `research/expansion-map-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Expansion Map
29
30> Based on: research/journey-map.md[, research/retention-map.md]
31> Date: YYYY-MM-DD
32
33## Summary
34## Expansion Triggers
35## Upgrade And Seat Growth Paths
36## Team Or Account Rollout
37## Referral And Advocacy Paths
38## Risks And Constraints
39## Product Gaps
40## Next Steps
41```
42
43## Alignment Page
44
45Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/expansion-map-{topic}.html`.
46
47## Constraints
48
49- Separate genuine expansion from ordinary retention.
50- For enterprise products, identify champion, buyer, admin, security, and procurement roles when relevant.
51- End with `## Next Steps`, preferring `$lifecycle-metrics`, `$monetization`, `$growth-model`, `$gtm` as context dictates.
GeorgeQLe