---
description: Design or audit the RevOps workflow from first touch to renewal, with SLAs, field ownership and proof reports
argument-hint: [motion or CRM or audit with history export paths]
---

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

Read martech-context/ first if it exists, especially stack.md, metrics.md, data-dictionary.md and decisions.md.
If $ARGUMENTS is empty or vague, ask whether this is a design or an audit, which motions are in scope, the CRM and edition, team coverage hours and time zones, and who owns each handoff.
For an audit, ask for read-only history exports of lifecycle stage, lead status, owner and deal stage, and request timestamps. Contact names, emails, phone numbers and free text are removed; keep the change source column, because user emails there become role labels through the source map.
Never ask for credentials, tokens or customer personal data. Work from record IDs, values, timestamps and sources, and never paste raw rows or addresses into the conversation.
Keep exports, configs and outputs in a working folder the user names, never in the skill folder.
Follow the skill's procedure in order, run its scripts when exports exist, and finish with its acceptance checks.
Never change stages, owners, workflows, assignment rules or properties in the CRM; the CRM admin applies the approved change list. Write to martech-context/ only after explicit approval.
Never submit forms, create test records, run imports or trigger workflows yourself; the CRM admin runs the rehearsal after the change list is approved, in a sandbox or on flagged test records with explicit approval.
Hand back the workflow spec, the SLA and field ownership registers, the report pack, audit findings with evidence, and a change list with a rehearsal plan a person can apply.

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