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.
Onboarding Map
Create the stage-level onboarding plan that expands research/journey-map.md.
Workflow
- Resolve app scope using the same
research/{app}/ convention as /journey-map.
- Require
research/journey-map.md or research/{app}/journey-map.md; if missing, recommend /journey-map.
- Load ICP, journey map, specs, customer feedback, metrics, and current product routes/components when present.
- Interview and recommend around: signup entry points, account creation, required setup, imports/integrations, team invites, empty states, first-session guidance, first 5 minutes/hour/day, aha threshold, drop-offs, recovery, and support touchpoints.
- Present the proposed onboarding model before writing.
- Write
research/onboarding-map.md and research/onboarding-map-interview.md after validation.
Output Shape
# Onboarding Map
> Based on: research/journey-map.md
> Date: YYYY-MM-DD
## Summary
## Personas And Entry Points
## Signup And Setup Flow
## Activation Path
## First Success
## Drop-Offs And Recovery
## Instrumentation Needs
## Product Gaps
## Next Steps
Alignment Page
Follow the shared Alignment Page convention in CLAUDE.md. Output: alignment/onboarding-map-{topic}.html.
Constraints
- Stay stage-specific; do not rewrite the whole journey map.
- Make onboarding steps concrete enough to drive specs, UX variations, and instrumentation.
- End with
## Next Steps, preferring /conversion-map, /lifecycle-metrics, /ux-variations as context dictates.
1---2name: onboarding-map-63description: Plan signup, setup, activation, first success, onboarding drop-offs, and time-to-value for each lifecycle persona4---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# Onboarding Map
11
12
13
14Create the stage-level onboarding plan that expands `research/journey-map.md`.
15
16## Workflow
17
181. Resolve app scope using the same `research/{app}/` convention as `/journey-map`.
192. Require `research/journey-map.md` or `research/{app}/journey-map.md`; if missing, recommend `/journey-map`.
203. Load ICP, journey map, specs, customer feedback, metrics, and current product routes/components when present.
214. Interview and recommend around: signup entry points, account creation, required setup, imports/integrations, team invites, empty states, first-session guidance, first 5 minutes/hour/day, aha threshold, drop-offs, recovery, and support touchpoints.
225. Present the proposed onboarding model before writing.
236. Write `research/onboarding-map.md` and `research/onboarding-map-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Onboarding Map
29
30> Based on: research/journey-map.md
31> Date: YYYY-MM-DD
32
33## Summary
34## Personas And Entry Points
35## Signup And Setup Flow
36## Activation Path
37## First Success
38## Drop-Offs And Recovery
39## Instrumentation Needs
40## Product Gaps
41## Next Steps
42```
43
44## Alignment Page
45
46Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/onboarding-map-{topic}.html`.
47
48## Constraints
49
50- Stay stage-specific; do not rewrite the whole journey map.
51- Make onboarding steps concrete enough to drive specs, UX variations, and instrumentation.
52- End with `## Next Steps`, preferring `/conversion-map`, `/lifecycle-metrics`, `/ux-variations` as context dictates.
GeorgeQLe