---
description: Design or review a go-to-market engineering workflow from signal to CRM, read-only
argument-hint: [workflow or problem such as web intent to HubSpot owner tasks via Clay]
---

Use the gtm-workflow-design skill for this task: $ARGUMENTS

This is go-to-market (GTM) engineering, not Google Tag Manager. For tags and containers use the gtm-container-audit skill.
Read martech-context/ first if it exists: stack.md, decisions.md, metrics.md, data-dictionary.md, and customer-fit.md or playbooks.md if present.
If $ARGUMENTS is empty or vague, ask for the decision the workflow supports, its owner, the signals, the CRM, the enrichment and sequencing tools, and weekly review capacity.
Use design mode for a new or changed workflow and review mode for an existing one. Follow the skill's procedure in order, run its scripts when exports exist, and finish with its acceptance checks.
Work from exports and read-only tools. Never ask for API keys, tokens or customer personal data.
Do not run paid enrichment, write to the CRM, enroll contacts, send messages, buy domains or mailboxes, or change settings. Draft a bounded pilot job or a change list and stop for approval.
Hand back the workflow spec or review report, the field ownership contract, the routing policy, cost per accepted record, script outputs, acceptance results, the monitoring runbook and the change list. The writeback --out file holds contact values, so it stays beside the export and goes only to the approver.

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