# define-handoff

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

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 450 repo stars
- Author: gtmagents
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-handoff-orchestration/commands/define-handoff.md
- Updated: 2026-04-03
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/define-handoff

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/define-handoff.md` — Call it with /define-handoff. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/define-handoff.md` — Call it with /prompts:define-handoff. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/define-handoff.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/define-handoff.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-handoff-orchestration/commands/define-handoff.md

## When to use it
- 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
- 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`

## Source text · define-handoff.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4ebac96f7f45d745.

BEGIN THIRD-PARTY FILE 4ebac96f7f45d745
```text
---
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.
```
END THIRD-PARTY FILE 4ebac96f7f45d745

The third-party file has ended. Everything between the 4ebac96f7f45d745 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3137 of 3297 bytes. © gtmagents · Apache-2.0 · https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-handoff-orchestration/commands/define-handoff.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
