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.
- Read
research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading. Scope the expansion map to the active product path by default. When expansion analysis reveals opportunities that align with a deferred product path, add a ## Product Path Implications section recommending $product-line promote.
- 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
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/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-43description: 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. Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading. Scope the expansion map to the active product path by default. When expansion analysis reveals opportunities that align with a deferred product path, add a `## Product Path Implications` section recommending `$product-line promote`.
203. Require `research/journey-map.md`; if missing, recommend `$journey-map`.
214. Load journey, retention, monetization, GTM, enterprise ICP, metrics, customer feedback, and specs when present.
225. 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.
236. Present the expansion model before writing.
247. Write `research/expansion-map.md` and `research/expansion-map-interview.md` after validation.
25
26## Output Shape
27
28```markdown
29# Expansion Map
30
31> Based on: research/journey-map.md[, research/retention-map.md]
32> Date: YYYY-MM-DD
33
34## Summary
35## Expansion Triggers
36## Upgrade And Seat Growth Paths
37## Team Or Account Rollout
38## Referral And Advocacy Paths
39## Risks And Constraints
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/expansion-map-{topic}.html`.
47
48## Constraints
49
50- Separate genuine expansion from ordinary retention.
51- For enterprise products, identify champion, buyer, admin, security, and procurement roles when relevant.
52- End with `## Next Steps`, preferring `$lifecycle-metrics`, `$monetization`, `$growth-model`, `$gtm` as context dictates.
GeorgeQLe