---
description: Design or review a martech integration with a written spec, field ownership, API budget, test plan and runbook
argument-hint: [flow such as Stripe subscriptions to HubSpot companies]
---

Use the martech-integration-engineering skill for this task: $ARGUMENTS

Read martech-context/ first if it exists, especially stack.md, data-dictionary.md and decisions.md.
If $ARGUMENTS is empty or vague, ask for the source and destination tools and objects, the decision the flow serves, volumes, how fresh the data must be, and the owners.
Say which mode applies: design a new flow, review an existing one, or recover from an outage, duplicate storm or backfill.
Follow the skill's procedure in order, run its scripts on the exports you have, and finish with its acceptance checks.
Never ask for API keys, tokens, signing secrets or customer records. Work from exports, sandbox payloads and read-only connections.
Do not change any connector, iPaaS scenario, sync, webhook subscription, CRM property or code, and do not replay or resend events. Produce drafts and a change list.
Ask for approval before any test that sends a message, creates a record, replays events or uploads data, in a sandbox or in production.
Hand back the integration spec, field ownership register (field map), sizing, test plan with evidence, runbook and change list; in review mode the review report and change list; in recover mode the recovery plan for a person to run. List the decisions still open.

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