Skip to main content
command CX Codex

define-handoff — Claude Code command: sales routing and SLA design

define-handoff — a command to design lead-to-sales handoff: sets routing rules, response SLAs, and enablement requirements for each sales pod or segment.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/define-handoff.md
Open on GitHub

What define-handoff does

define-handoff structures the entire handoff flow: from funnel stage definitions and qualification criteria through lead distribution logic, SLA feasibility, and sales team readiness. It works with segments (enterprise, mid-market, SMB, partner), business goals (pipeline, expansion, product activation, ABM), and response-time constraints on first contact.

The process unfolds in five steps: confirm funnel and qualification criteria, map routing logic (account owner, round-robin, pod-based), model achievable response times against capacity, list required assets and talk tracks per pod, prepare approval documentation. Outputs include routing matrix, SLA tables, data and tooling checklist with owners, enablement kit request, and plan entry logged in .claude/plans for audit.

The command invokes specialised skills: revops-director leads routing and SLA design, routing-logic enforces qualification standards, enablement-kit verifies asset readiness. If SLA breaches or routing failures repeat twice in 48 hours, an escalation to sales and marketing leadership triggers.

What it helps with

  • design lead distribution across sales reps without gaps or bottlenecks
  • set realistic response times given actual team capacity
  • confirm sales reps are ready with scripts, sequences, and dashboards
  • document everything for leadership sign-off

Example prompts for the agent

  • Design routing for enterprise segment targeting pipeline growth with 2-hour SLA: /sales-handoff-orchestration:define-handoff --segment enterprise --goal pipeline --response-sla 2h
  • Model handoff for SMB expansion with limited SDR capacity and existing sequences: /sales-handoff-orchestration:define-handoff --segment SMB --goal expansion --capacity limited --dependencies sequences
  • Plan ABM campaign with RevOps Director escalation path: /sales-handoff-orchestration:define-handoff --segment enterprise --goal ABM --response-sla 1d

How to install define-handoff

Manually: put the files in place

.claude/commands/define-handoff.md

Call it with /define-handoff. For all projects use ~/.claude/commands/

Questions about define-handoff

How do I install define-handoff in Claude Code?

Save the command file to .claude/commands/define-handoff.md. It loads on Claude Code startup. Call it as /sales-handoff-orchestration:define-handoff with your required flags.

What does define-handoff do?

It designs the entire lead-to-sales workflow: sets qualification criteria, maps distribution logic, calculates realistic SLAs, prepares enablement materials, and generates sign-off documentation for leadership.

What parameters are required?

Required: segment (enterprise, mid-market, SMB, partner), business goal (pipeline, expansion, product activation, ABM), and response SLA (e.g. 2h or 1d). Optional: SDR/AE capacity notes and dependency status (scoring, sequences, talk tracks).

Source text

define-handoff.md · Apache-2.0
---
name: define-handoff
description: Establishes marketing-to-sales routing design, SLAs, and enablement requirements.
usage: /sales-handoff-orchestration:define-handoff --segment enterprise --goal pipeline --response-sla 2h
---

# Command: define-handoff

## Inputs
- **segment** – target segment/persona (enterprise, mid-market, SMB, partner).
- **goal** – business target (pipeline, expansion, product activation, ABM campaign).
- **response-sla** – desired first-touch SLA (e.g., 2h, 1d).
- **capacity** – optional SDR/AE capacity notes to shape routing rules.
- **dependencies** – optional systems/content that must be ready (scoring, sequences, talk tracks).

### GTM Agents Pattern & Plan Checklist
> Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Handoff design usually follows a **pipeline** (intake → routing → SLA modeling → enablement → approvals). If routing + enablement prep can run in parallel, log a **diamond** segment with merge gate.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, tasks, dependencies (data, tooling), context passing (scoring configs), error handling, and success metrics (SLA %, acceptance rate, conversion lift).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for CRM/MAP script diffs, Context7 for platform docs, Sequential Thinking for review cadence, Playwright for QA of lead forms/sequences.
- **Guardrails**: Default retry limit = 2 for automation/build failures; escalation ladder = RevOps Director → Sales Manager → CRO.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.

## Workflow
1. **Brief Intake** – confirm funnel stage definitions, qualification criteria, scoring thresholds.
2. **Routing Blueprint** – map lead ownership logic (account owner, round-robin, pod based) and required enrichment data.
3. **SLA Modeling** – calculate achievable response times vs capacity, flag risks, define escalation ladder.
4. **Enablement Requirements** – list assets, talk tracks, sequences, and dashboards each pod needs.
5. **Approval Packet** – consolidate documentation for RevOps + sales leadership sign-off.

## Outputs
- Handoff design doc (routing matrix, SLA tables, escalation tree).
- Data + tooling checklist (fields, integrations, automation flows) with owners.
- Enablement kit request list with due dates.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `revops-director` – leads routing/SLA design.
- `routing-logic` skill – enforces qualification + assignment best practices.
- `enablement-kit` skill – ensures supporting assets are ready.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Sales Manager covering RevOps Director) when specialists unavailable.
- **Escalation triggers**: if SLA breaches or routing failures exceed guardrails twice in 48h, trigger escalation to Sales + Marketing leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON whenever segments, routing logic, or enablement requirements change so audit trail mirrors GTM Agents standards.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Automation and no-code: n8n, Zapier, Make →
narrative-enablement-kit aaron-he-zhu narrative-enablement-kit builds a shared messaging kit from an existing narrative canon: pitch lengths, spokesperson answers, boilerplate, bios, and language rules. It turns approved brand material into repeatable guidance. CX Codex +1 1,100installs service-itsm-agentic-setup-incident-sla-configure forcedotcom service-itsm-agentic-setup-incident-sla-configure sets up end-to-end Incident SLA pipelines in Salesforce Service Cloud ITSM via the headless-360 MCP server. Configures policies, milestones, and entitlements. CX Codex +1 1,200installs sales-coaching-plan-generator OneWave-AI sales-coaching-plan-generator builds individual development plans around a rep's weak spots: skill assessments, call reviews, ride-along checklists, certification tracking. CX Codex +1 369installs inbound-lead-qualifier OneWave-AI inbound-lead-qualifier — a skill for Claude Code, Codex, Cursor, and five other platforms that scores inbound leads against ICP fit, intent and urgency, then routes them to the right sales rep with a call script and qualification questions. CX Codex +1 343installs define-jtbd-canvas product-on-purpose The define-jtbd-canvas skill builds a Jobs to be Done canvas covering the functional, emotional and social sides of a customer job. Useful when you need to understand motivation before building. CX Codex +1 862installs asb-carol-define asmartbear asb-carol-define turns your working files on strengths, keystones, deal-breakers and inciting events into CAROL.md, a definition of the ideal customer. CX Codex +1 732installs

From the same set224

The whole set →
track-source track-source combines partner campaign data and produces attribution reporting with revenue contributions and suggested changes. Use it to review co-marketing results. CX Codex +1 ★ 450repo stars manage-assets manage-assets — a command for orchestrating co-branded asset production, approvals, and distribution across partner teams. Tracks asset inventory, routes review workflows, and packages deliverables for activation. CX Codex +1 ★ 450repo stars optimize-referrals optimize-referrals analyzes referral conversion funnels, fraud patterns, and partner health to generate structured optimization plans in Claude Code. CX Codex +1 ★ 450repo stars synthesize-feedback The synthesize-feedback command turns customer signals into ranked themes and estimates their impact. Use it to prepare evidence and follow-up priorities from feedback. CX Codex +1 ★ 450repo stars monitor-personalization monitor-personalization audits personalization campaigns, tracks experiment outcomes, and flags consent violations across user segments. CX Codex +1 ★ 450repo stars editorial-ops editorial-ops is a Claude Code skill that plans multi-channel editorial calendars and coordinates GTM content production from ideation through distribution, with KPI guardrails set before assets ship. CX Codex +1 ★ 450repo stars measure-engagement measure-engagement pulls community health metrics, sentiment, and experiment results into one report with a prioritized action list. Use it when you need to see what is happening in a community and what to do about it. CX Codex +1 ★ 450repo stars prioritize-gaps prioritize-gaps scores customer journey friction points, assigns owners, and creates remediation roadmaps. Helps teams prioritize fixes across onboarding and lifecycle stages. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open