---
description: Build a tracking plan for one customer journey as testable event contracts
argument-hint: [journey, e.g. trial signup to first report]
---

Use the tracking-plan-builder skill for this task: $ARGUMENTS

Read martech-context/ first if it exists: stack.md, naming-rules.md, metrics.md, data-dictionary.md, decisions.md and tracking-plan/.
Reuse any contract that already exists. Never write a second definition of the same event.
If $ARGUMENTS is empty or vague, ask for the journey, the decision it supports, the systems and tools involved, the identity and consent model, and the owners.
Follow the skill's procedure in order and run its acceptance checks, including the collision check, before you hand anything back.
Do not ask for or store credentials, tokens or customer records. Use test or redacted payloads only.
Stop for approval before writing to martech-context/ or .amplitude/, and before any change to a vendor tool, tag manager, CRM or other live system.
Hand back the journey, the event contracts, destination mappings, acceptance tests and the list of proposed files, with anything still open.

If the tracking-plan-builder skill is not installed, install it with: npx skills add https://www.martechdevs.com --skill tracking-plan-builder -a claude-code
