---
description: Find the first layer where a tracking problem starts, prove it and draft the fix
argument-hint: [metric, symptom or journey]
---

Use the tracking-break-map skill for this task: $ARGUMENTS

Read martech-context/ first if it exists: stack.md, tracking-plan/, metrics.md and decisions.md.
If the request is empty or vague, ask for the metric, report, date range, timezone and what it was compared with.
Ask for a daily backend count of the same outcome and the change log for the window before opening any configuration.
Follow the skill's procedure in order and check every acceptance check before you call it done.
Work read-only. Stop for approval before changing any live system, including GTM, GA4, Google Ads or data models.
Hand back the break-map record, the proven failing layer with evidence, the draft fix with its owner and the retest plan.

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