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 npx skillpacks install <pack> from the project shell, instead of the target skill.
Transaction Map
Invoke as $transaction-map.
Map the operational transaction flow after a customer decides to buy or upgrade.
Process
0. Product-Path Scope Resolution
Resolve research scope by product path before using code or app structure as a hint:
- If
$ARGUMENTS names a non-archived research/{slug}/ directory or a product-path ID whose scope_path points there, use that path. Treat {slug} as the product/app name, not the ICP, audience, or segment label.
- If
$ARGUMENTS names only research/_archive/{slug}/ or a manifest entry with status: archived or legacy status: abandoned, stop and warn that the path is archived; do not write or update scoped outputs there.
- Read
research/.progress.yaml when present. Normalize legacy active_path to active_paths on read and write back active_paths on manifest updates. Treat legacy abandoned as archived; exclude archived, abandoned, deferred, revisit_candidate, promoted, and any scope_path under research/_archive/ from active target selection.
- If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
- If no active manifest target exists, list non-archived product directories under
research/, excluding research/_archive/ and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
- If no product directories exist, use flat
research/ single-product mode.
- Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing
research/{slug}/ product path when code clearly exposes an app, but do not require code or monorepo detection before using research/{slug}/.
When product path {slug} is active, read and write research under research/{slug}/, specs under specs/{slug}/, and treat top-level research/*.md files as flat-mode documents or cross-path summaries.
- Resolve product-path scope using
research/{slug}/ when applicable.
- Read
research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading; treat legacy abandoned as archived and exclude archived/deferred/revisit/promoted paths plus research/_archive/ scopes from active target selection. 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 in flat mode, or research/{slug}/transaction-map.md and research/{slug}/transaction-map-interview.md when product-path scope is active, 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 via the packaged convention resolver; output path is 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.
Default Shipping Contract
Follow the shared shipping contract convention in CLAUDE.md.
1---2name: transaction-map3description: 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 `npx skillpacks install <pack>` from the project shell, instead of the target skill.
9
10# Transaction Map
11
12Invoke as `$transaction-map`.
13
14Map the operational transaction flow after a customer decides to buy or upgrade.
15
16## Process
17
18### 0. Product-Path Scope Resolution
19
20Resolve research scope by product path before using code or app structure as a hint:
21
221. If `$ARGUMENTS` names a non-archived `research/{slug}/` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product/app name, not the ICP, audience, or segment label.
232. If `$ARGUMENTS` names only `research/_archive/{slug}/` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.
243. Read `research/.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research/_archive/` from active target selection.
254. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
265. If no active manifest target exists, list non-archived product directories under `research/`, excluding `research/_archive/` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
276. If no product directories exist, use flat `research/` single-product mode.
287. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing `research/{slug}/` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research/{slug}/`.
29
30When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`, and treat top-level `research/*.md` files as flat-mode documents or cross-path summaries.
31
321. Resolve product-path scope using `research/{slug}/` when applicable.
332. Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived/deferred/revisit/promoted paths plus `research/_archive/` scopes from active target selection. Scope the transaction map to the active product path by default.
343. Require `research/journey-map.md`; recommend `$conversion-map` first when conversion decision logic is missing.
354. Load journey map, conversion map, monetization docs, specs, codebase payment routes/providers, support/refund policy docs, and customer feedback when present.
365. 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.
376. Present transaction states and failure modes before writing.
387. Write `research/transaction-map.md` and `research/transaction-map-interview.md` in flat mode, or `research/{slug}/transaction-map.md` and `research/{slug}/transaction-map-interview.md` when product-path scope is active, after validation.
39
40## Output Shape
41
42```markdown
43# Transaction Map
44
45> Based on: research/journey-map.md[, research/conversion-map.md]
46> Date: YYYY-MM-DD
47
48## Summary
49## Transaction Types
50## Checkout And Payment Flow
51## Provisioning And Fulfillment
52## Receipts, Invoices, And Records
53## Failure, Refund, And Dispute States
54## Trust And Support Touchpoints
55## Product Gaps
56## Next Steps
57```
58
59## Alignment Page
60
61Follow the shared alignment-page convention via the packaged convention resolver; output path is `alignment/transaction-map-{topic}.html`.
62
63## Constraints
64
65- Keep the map provider-agnostic unless the codebase or specs already choose a payment provider.
66- Identify compliance, tax, or legal questions as gaps; do not invent policy.
67- End with `## Next Steps`, preferring `$retention-map`, `$guide`, or `$lifecycle-metrics` as context dictates.
68
69## Default Shipping Contract
70
71Follow the shared shipping contract convention in CLAUDE.md.
72
GeorgeQLe