zhongwei/gh-gtmagents-gtm-agents-plugins-sales-handoff-orchestration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:31:43 +08:00
commit b7f5d993a7
12 changed files with 421 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
commands/define-handoff.md Normal file
View File

@@ -0,0 +1,48 @@
---
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.
---

48
commands/monitor-sla.md Normal file
View File

@@ -0,0 +1,48 @@
---
name: monitor-sla
description: Tracks MQL→SQL SLA performance, raises alerts, and recommends corrective actions.
usage: /sales-handoff-orchestration:monitor-sla --segment enterprise --window 7d --threshold 85
---
# Command: monitor-sla
## Inputs
- **segment** – filter for program/team to analyze.
- **window** – time period (24h, 7d, 30d) for metrics.
- **threshold** – SLA compliance target percentage.
- **notify** – optional channel or email for alert delivery.
- **dimensions** – optional breakdowns (owner, geo, campaign).
### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: SLA monitoring usually follows a **pipeline** (aggregation → calculation → diagnostics → actions → alerts). If diagnostics + recommendations can run in parallel, log a **diamond** segment and merge gate.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, data sources, task IDs, dependencies (dashboards, alert channels), error handling, and success metrics (SLA %, response time, queue depth).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for CRM automation diffs, Context7 for MAP/CRM field docs, Sequential Thinking for retro cadence, Playwright for form QA when routing fixes require front-end checks.
- **Guardrails**: Default retry limit = 2 for failed data pulls/alerts; escalation ladder = RevOps Director → Sales Manager → CRO.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm agents, dependencies, deliverables.
## Workflow
1. **Data Aggregation** – pull MAP/CRM timestamps (MQL created, accepted, touched) plus routing metadata.
2. **SLA Calculation** – compute response time, acceptance time, conversion rates vs targets.
3. **Drill-down Diagnostics** – highlight segments, owners, or campaigns below threshold.
4. **Action Recommendations** – prescribe playbooks (re-prioritize queues, add enablement, adjust routing rules).
5. **Alert Packaging** – send summary + deep dive dashboards to notify channels.
## Outputs
- SLA dashboard snapshot with compliance %, aging pipeline, at-risk cohorts.
- Recommendation list with owners and due dates.
- Optional incident ticket for severe breaches.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `revops-director` – reviews systemic issues and approves remediation.
- `sla-tracking` skill – ensures methodology + thresholds are standardized.
- `routing-logic` skill – recommends rule adjustments causing delays.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Sales Manager covering RevOps Director) when specialists unavailable.
- **Escalation triggers**: if SLA compliance stays below threshold for two consecutive windows, trigger escalation to Sales + Marketing leadership and open an incident per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever thresholds, alert channels, or remediation playbooks change.
---

48
commands/run-standups.md Normal file
View File

@@ -0,0 +1,48 @@
---
name: run-standups
description: Facilitates daily MQL→SQL standups with shared metrics, blockers, and follow-up actions.
usage: /sales-handoff-orchestration:run-standups --segment enterprise --hosts "revops,sales" --mode async
---
# Command: run-standups
## Inputs
- **segment** – pipeline segment or program focus for the standup.
- **hosts** – comma-separated facilitators (revops, marketing, sales, cs).
- **mode** – live | async to determine meeting vs async summary.
- **interval** – default daily; override for weekly/bi-weekly.
- **notes** – optional agenda additions or urgent topics.
### GTM Agents Pattern & Plan Checklist
> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Standups typically run **pipeline** (data prep → agenda → discussion → broadcast → accountability). If discussion capture + broadcast can run in parallel (async mode), document a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, schedule, task IDs, dependencies (dashboards, channels), error handling, and success metrics (response SLAs, blocker resolution %, queue depth).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for CRM report diffs, Context7 for platform docs, Sequential Thinking for retro notes, Playwright for verifying embedded dashboard links if needed.
- **Guardrails**: Default retry limit = 2 for data fetch/broadcast failures; escalation ladder = Lifecycle Coordinator → Sales Manager → RevOps Director.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm hosts, dependencies, deliverables.
## Workflow
1. **Data Prep** – pull latest routing stats (volume, conversion, SLA, backlog) filtered by segment.
2. **Agenda Builder** – auto-generate talking points: wins, blockers, experiments, escalations.
3. **Discussion Capture** – log owner + next action per issue, reference enablement resources.
4. **Broadcast** – send recap to shared channel/email with dashboards and follow-up tasks.
5. **Accountability Tracking** – sync action items into RevOps tracker for follow-up in next standup.
## Outputs
- Standup agenda doc (metrics snapshot, topics, owners).
- Action log with due dates and linked dashboards.
- Optional async update message for teams that cannot attend live.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `lifecycle-coordinator` – surfaces queue status + blockers.
- `sales-manager` – adds coaching notes + follow-up expectations.
- `enablement-kit` skill – links relevant scripts, talk tracks, or collateral.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., RevOps Director covering Lifecycle Coordinator) when specialists unavailable.
- **Escalation triggers**: if blockers remain unresolved for two standups or SLAs keep missing, escalate to Sales + Marketing leadership per GTM Agents rip-cord playbook.
- **Plan maintenance**: update plan JSON/change log whenever cadence, hosts, or tooling links change to maintain GTM Agents-grade auditability.
---