---
description: Check a Braze setup or Canvas, write a test plan, or find why a message was missed
argument-hint: [Canvas, journey or incident]
---

Use the braze-implementation-qa skill for this task: $ARGUMENTS

Read martech-context/ first if it exists, especially stack.md, the tracking plan, the data dictionary and decisions.md.
If $ARGUMENTS is empty or vague, ask whether this is a new setup, a launch review of one Canvas, or a missing or unwanted message.
Then ask for the journey spec, every system that writes to Braze, and the Canvas and workspace settings.
For an incident, ask for the test profile's external_id, expected and observed behaviour, and timestamps, and capture short-lived logs first.
Follow the skill's procedure and acceptance checks in order. Use test profiles only and never generate load against Braze.
Stop for approval before any write: profile updates, Canvas triggers, setting changes, identify, merge or control group changes.
Hand back the identity contract, trigger contract, control sheet and test plan, or a diagnosis naming the first failing gate.

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