Skip to main content
command CX Codex

trigger-plays — Claude Code command: setup and use

trigger-plays is a Claude Code command that starts multi-channel campaigns from live signals and checks suppression rules. It tracks SLA status and campaign results.

Apache-2.0 ★ 450 updated 2026-04-03

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

What trigger-plays does

The command checks account eligibility against signal thresholds and suppression rules, then builds a campaign from a selected playbook. It assigns actions, timing, and owners across sales, ads, email, web, or events, and sends tasks to CRM and engagement tools.

Before launch, the workflow calls for a dependency, approval, and suppression review using docs/usage-guide.md#orchestration-best-practices-puerto-parity. The plan is stored in .claude/plans/plan-<timestamp>.json with accounts, dependencies, error handling, and success measures. Failed task pushes or syncs have a retry limit of 2. After two SLA breaches or a suppression conflict, the play is halted and remediation is logged.

Outputs include an activation manifest, an SLA dashboard snapshot, webhook notifications, and a post-play measurement brief template. A predefined playbook ID and account list are required; signal filters and suppression can be supplied as additional inputs.

What it helps with

  • start a campaign for accounts matching live signals
  • assign playbook actions across selected channels
  • track SLA breaches and campaign conflicts
  • halt a play when suppression rules conflict

Example prompts for the agent

  • Start the executive-briefing playbook for accounts in file://accounts.csv across sales, ads, and email with /intent-signal-orchestration:trigger-plays.
  • Run surge-outreach for accounts acct-101,acct-102 with the surge signal using /intent-signal-orchestration:trigger-plays.
  • Launch nurture-reset for file://accounts.csv on email and web, with suppression enabled, using /intent-signal-orchestration:trigger-plays.

How to install trigger-plays

Manually: put the files in place

.claude/commands/trigger-plays.md

Call it with /trigger-plays. For all projects use ~/.claude/commands/

Questions about trigger-plays

How do I install trigger-plays in Claude Code?

Save the command file at .claude/commands/trigger-plays.md in the project.

What does trigger-plays do?

It selects eligible accounts, assembles a campaign from a predefined playbook, and runs its actions across chosen channels. It also records a plan and monitors SLA status.

What inputs does trigger-plays need?

Provide a predefined playbook ID and accounts as a CSV or JSON path, or as a list of account IDs. Channels are supplied as a list; signal filters and suppression are optional.

Source text

trigger-plays.md · Apache-2.0
---
name: trigger-plays
description: Launches multi-channel plays based on live signals with safeguards, SLA tracking, and measurement hooks.
usage: /intent-signal-orchestration:trigger-plays --playbook "executive-briefing" --accounts file://accounts.csv --channels "sales,ads,email"
---

# Command: trigger-plays

## Inputs
- **playbook** – required identifier referencing a predefined program (executive-briefing, surge-outreach, nurture-reset).
- **accounts** – CSV/JSON path or comma list of account IDs to activate.
- **channels** – comma-separated list (sales, ads, email, web, events).
- **signals** – optional signal filters or thresholds.
- **suppress** – true/false to enforce global suppression logic before triggering.

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

- **Pattern selection**: Activation typically runs **pipeline** (eligibility → play assembly → channel execution → telemetry → monitoring). If channel execution fan-out is large, log a **fan-out** section with reconverge guardrail in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing playbook, account set, dependency graph (automation, sales, marketing), error handling, and success metrics (SLA adherence, reply/conversion lift, suppression integrity).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for playbook diffs, Context7 for SOPs/runbooks, Sequential Thinking for go/no-go reviews, Playwright for landing page or form QA.
- **Guardrails**: Default retry limit = 2 for failed task pushes or syncs; escalation ladder = Automation Lead → Sales Ops/Marketing Ops → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before triggering to confirm dependencies, approvals, and suppression compliance.

## Workflow
1. **Eligibility Check** – confirm each account meets signal thresholds and is not suppressed.
2. **Play Assembly** – map approved accounts to playbook actions, cadences, and owners.
3. **Channel Execution** – push tasks to CRM/engagement tools, sync audiences to ads, and schedule nurture branches.
4. **Telemetry Setup** – attach UTM parameters, experiment IDs, and success metrics per channel.
5. **Monitoring & Escalation** – track SLA adherence, bouncebacks, or conflicts; notify owners when intervention is needed.

## Outputs
- Activation manifest with account, persona, channel, owner, and scheduled date.
- SLA dashboard snapshot plus webhook notifications for go-live.
- Post-play measurement brief template for RevOps + GTM leads.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `automation-lead` – ensures executions honor routing/suppression rules.
- `sales-liaison` – coordinates rep-owned steps.
- `outbound-plays` skill – provides channel-specific messaging + cadences.
- `suppression-logic` skill – runs compliance + conflict checks.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Sales Liaison covering Automation Lead) when leads unavailable.
- **Escalation triggers**: if SLA breaches occur twice or suppression conflicts trigger, execute GTM Agents rip-cord, halt plays, and log remediation in plan JSON.
- **Plan maintenance**: update plan JSON/change log when playbooks, account lists, or channel mix change to preserve audit traceability.

---

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

Similar slash commands

All slash commands for Automation and no-code: n8n, Zapier, Make →

From the same set224

The whole set →
experiment-design-kit experiment-design-kit structures product and growth hypotheses into test briefs with guardrails, variant catalogs, and rollback plans. CX Codex +1 ★ 450repo stars run-community-event run-community-event is a Claude Code command that drafts an agenda, moderation plan, and follow-up tasks for a community session or livestream. CX Codex +1 ★ 450repo stars cold-email-personalization cold-email-personalization turns a prospect brief into a cold email and a follow-up series: research first, a 60-120 word draft, then a scored QA pass. CX Codex +1 ★ 450repo stars run-retro run-retro orchestrates renewal cycle retrospectives to analyze ARR shifts, review churn patterns, and generate action trackers. CX Codex +1 ★ 450repo stars orchestrate-renewal-play orchestrate-renewal-play builds a renewal play with timeline, owner tasks, and escalation paths. Use it when an account slips toward red and needs a structured save motion. CX Codex +1 ★ 450repo stars route-insights route-insights routes customer feedback themes to functional owners, creates communication plans, and sets up tracking loops. Useful for moving raw customer insights into engineering or CS backlogs. CX Codex +1 ★ 450repo stars exec-dashboard-blueprint exec-dashboard-blueprint is a Claude Code skill for structuring board-ready marketing dashboards around a Story Arc. It organizes /marketing-analytics output into KPIs, risks, and actions with owners and due dates. CX Codex +1 ★ 450repo stars lifecycle-mapping lifecycle-mapping splits lifecycle automation into stages, signals, touches and SLA rules, with room for tests. Useful when onboarding or retention programs need one shared scheme. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open