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.
Conversion Map
Map how evaluators become customers, including the decision path from first value to commitment.
Workflow
- Resolve app scope using
research/{app}/ when applicable.
- Require
research/journey-map.md; if missing, recommend /journey-map.
- Load ICP, journey map, onboarding map, competitive analysis, monetization/GTM docs, specs, and feedback when present.
- Interview and recommend around: evaluation mode, trial/freemium/demo motion, buyer and user roles, proof required, conversion trigger, objections, pricing/packaging concerns, sales assist, procurement, timeline, and lost-deal reasons.
- Present the conversion model and unresolved assumptions before writing.
- Write
research/conversion-map.md and research/conversion-map-interview.md after validation.
Output Shape
# Conversion Map
> Based on: research/journey-map.md
> Date: YYYY-MM-DD
## Summary
## Evaluation Path
## Buyer And Decision Roles
## Conversion Trigger
## Objections And Proof
## Pricing And Packaging Implications
## Drop-Offs And Recovery
## Product Gaps
## Next Steps
Alignment Page
Follow the shared Alignment Page convention in CLAUDE.md. Output: alignment/conversion-map-{topic}.html.
Constraints
- Keep conversion separate from payment mechanics; use
/transaction-map for checkout, payments, fulfillment, refunds, and receipts.
- End with
## Next Steps, preferring /transaction-map, /monetization, /gtm, /experiment as context dictates.
1---2name: conversion-map-63description: Plan evaluation, trial, pricing decision, objections, buyer roles, and conversion triggers4---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# Conversion Map
11
12
13
14Map how evaluators become customers, including the decision path from first value to commitment.
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 ICP, journey map, onboarding map, competitive analysis, monetization/GTM docs, specs, and feedback when present.
214. Interview and recommend around: evaluation mode, trial/freemium/demo motion, buyer and user roles, proof required, conversion trigger, objections, pricing/packaging concerns, sales assist, procurement, timeline, and lost-deal reasons.
225. Present the conversion model and unresolved assumptions before writing.
236. Write `research/conversion-map.md` and `research/conversion-map-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Conversion Map
29
30> Based on: research/journey-map.md
31> Date: YYYY-MM-DD
32
33## Summary
34## Evaluation Path
35## Buyer And Decision Roles
36## Conversion Trigger
37## Objections And Proof
38## Pricing And Packaging Implications
39## Drop-Offs And Recovery
40## Product Gaps
41## Next Steps
42```
43
44## Alignment Page
45
46Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/conversion-map-{topic}.html`.
47
48## Constraints
49
50- Keep conversion separate from payment mechanics; use `/transaction-map` for checkout, payments, fulfillment, refunds, and receipts.
51- End with `## Next Steps`, preferring `/transaction-map`, `/monetization`, `/gtm`, `/experiment` as context dictates.
GeorgeQLe