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.
Transaction Map
Map the operational transaction flow after a customer decides to buy or upgrade.
Workflow
- Resolve app scope using
research/{app}/ when applicable.
- Require
research/journey-map.md; recommend /conversion-map first when conversion decision logic is missing.
- Load journey map, conversion map, monetization docs, specs, codebase payment routes/providers, support/refund policy docs, and customer feedback when present.
- Interview and recommend around: checkout entry, plan/quantity selection, payment states, tax/invoice needs, account provisioning, fulfillment, receipts, failed payment recovery, refunds, cancellations, disputes, trust/safety messages, and support handoff.
- Present transaction states and failure modes before writing.
- Write
research/transaction-map.md and research/transaction-map-interview.md after validation.
Output Shape
# Transaction Map
> Based on: research/journey-map.md[, research/conversion-map.md]
> Date: YYYY-MM-DD
## Summary
## Transaction Types
## Checkout And Payment Flow
## Provisioning And Fulfillment
## Receipts, Invoices, And Records
## Failure, Refund, And Dispute States
## Trust And Support Touchpoints
## Product Gaps
## Next Steps
Alignment Page
Follow the shared Alignment Page convention in CLAUDE.md. Output: alignment/transaction-map-{topic}.html.
Constraints
- Keep the map provider-agnostic unless the codebase or specs already choose a payment provider.
- Identify compliance, tax, or legal questions as gaps; do not invent policy.
- End with
## Next Steps, preferring /retention-map, /guide, or /lifecycle-metrics as context dictates.
1---2name: transaction-map-63description: Plan purchase, checkout, payment, fulfillment, receipt, refund, dispute, and trust-state flows4---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# Transaction Map
11
12
13
14Map the operational transaction flow after a customer decides to buy or upgrade.
15
16## Workflow
17
181. Resolve app scope using `research/{app}/` when applicable.
192. Require `research/journey-map.md`; recommend `/conversion-map` first when conversion decision logic is missing.
203. Load journey map, conversion map, monetization docs, specs, codebase payment routes/providers, support/refund policy docs, and customer feedback when present.
214. Interview and recommend around: checkout entry, plan/quantity selection, payment states, tax/invoice needs, account provisioning, fulfillment, receipts, failed payment recovery, refunds, cancellations, disputes, trust/safety messages, and support handoff.
225. Present transaction states and failure modes before writing.
236. Write `research/transaction-map.md` and `research/transaction-map-interview.md` after validation.
24
25## Output Shape
26
27```markdown
28# Transaction Map
29
30> Based on: research/journey-map.md[, research/conversion-map.md]
31> Date: YYYY-MM-DD
32
33## Summary
34## Transaction Types
35## Checkout And Payment Flow
36## Provisioning And Fulfillment
37## Receipts, Invoices, And Records
38## Failure, Refund, And Dispute States
39## Trust And Support Touchpoints
40## Product Gaps
41## Next Steps
42```
43
44## Alignment Page
45
46Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/transaction-map-{topic}.html`.
47
48## Constraints
49
50- Keep the map provider-agnostic unless the codebase or specs already choose a payment provider.
51- Identify compliance, tax, or legal questions as gaps; do not invent policy.
52- End with `## Next Steps`, preferring `/retention-map`, `/guide`, or `/lifecycle-metrics` as context dictates.
GeorgeQLe