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.
- Read
research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading. Scope the transaction map to the active product path by default.
- 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
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/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-73description: 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. Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading. Scope the transaction map to the active product path by default.
203. Require `research/journey-map.md`; recommend `/conversion-map` first when conversion decision logic is missing.
214. Load journey map, conversion map, monetization docs, specs, codebase payment routes/providers, support/refund policy docs, and customer feedback when present.
225. 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.
236. Present transaction states and failure modes before writing.
247. Write `research/transaction-map.md` and `research/transaction-map-interview.md` after validation.
25
26## Output Shape
27
28```markdown
29# Transaction Map
30
31> Based on: research/journey-map.md[, research/conversion-map.md]
32> Date: YYYY-MM-DD
33
34## Summary
35## Transaction Types
36## Checkout And Payment Flow
37## Provisioning And Fulfillment
38## Receipts, Invoices, And Records
39## Failure, Refund, And Dispute States
40## Trust And Support Touchpoints
41## Product Gaps
42## Next Steps
43```
44
45## Alignment Page
46
47When 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/transaction-map-{topic}.html`.
48
49## Constraints
50
51- Keep the map provider-agnostic unless the codebase or specs already choose a payment provider.
52- Identify compliance, tax, or legal questions as gaps; do not invent policy.
53- End with `## Next Steps`, preferring `/retention-map`, `/guide`, or `/lifecycle-metrics` as context dictates.
GeorgeQLe