orchestrate-renewal-play — Claude Code command for renewal plays
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.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/orchestrate-renewal-play.mdWhat orchestrate-renewal-play does
The command runs a cross-functional renewal motion from a chosen playbook. It takes an account, a segment (strategic, growth, scale), a risk level, and a deadline. Risk sets the default cadence and oversight.
Five steps sit inside: pull forecast, usage, sentiment and open issues; tailor the play to the persona stack and risk; hand out tasks to CSM, AE, exec sponsor, product and finance; attach decks, ROI analyses and roadmap updates; log checkpoints and escalation triggers. The plan lands in .claude/plans/plan-<timestamp>.json.
The workflow leans on the stack from docs/gtm-essentials.md — Serena, Context7, Sequential Thinking, Playwright. If that file and the tool hooks are not set up, parts of the run will fall flat. Retry limit is 2 by default; escalation follows CSM → Renewal Director → CRO/Exec Sponsor.
What it helps with
- assemble a renewal plan with timeline and owners
- match a playbook to account risk tier
- assign tasks across CSM, AE, sponsor, product, finance
- put together the client-facing enablement packet
- set checkpoints and escalation triggers
Example prompts for the agent
- Run a renewal play for ACME Corp: strategic tier, red risk, exec-save play
- Build a renewal plan with a March 15 deadline and the value-realization play
- Orchestrate renewal tasks for account 88421, yellow risk, adoption-accelerator play
How to install orchestrate-renewal-play
Manually: put the files in place
.claude/commands/orchestrate-renewal-play.mdCall it with /orchestrate-renewal-play. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/orchestrate-renewal-play.mdCall it with /prompts:orchestrate-renewal-play. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/orchestrate-renewal-play.prompt.mdManually: put the files in place
.gemini/commands/orchestrate-renewal-play.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about orchestrate-renewal-play
How do I install orchestrate-renewal-play in Claude Code?
Drop the command file into .claude/commands/orchestrate-renewal-play.md. It then runs as /renewal-orchestration:orchestrate-renewal-play.
What does orchestrate-renewal-play do?
It builds a renewal motion: pulls account context, customizes the play to risk and segment, splits tasks among owners, and lays out an escalation path. Output is a packet with timeline, owners, and talking points.
Which playbooks can the command run?
Four are available: exec-save, value-realization, pricing-refresh, adoption-accelerator. Pick one with the --play argument.
Source text
orchestrate-renewal-play.md · Apache-2.0
--- name: orchestrate-renewal-play description: Coordinates cross-functional renewal motions with timelines, stakeholder tasks, and escalation paths. usage: /renewal-orchestration:orchestrate-renewal-play --account "ACME Corp" --tier strategic --risk red --play "exec-save" --- # Command: orchestrate-renewal-play ## Inputs - **account** – required account name or ID. - **tier** – strategic | growth | scale segments. - **risk** – green | yellow | red (sets default cadence + oversight). - **play** – playbook identifier (exec-save, value-realization, pricing-refresh, adoption-accelerator). - **deadline** – renewal date or milestone to anchor the plan. ### GTM Agents Pattern & Plan Checklist > Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Renewal plays generally run **pipeline** (context → customization → tasks → enablement → governance). If enablement + task orchestration can run in parallel, log a **diamond** segment with merge gate. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, risk tier, task IDs, parallel groups, dependency graph (exec sponsor, product, finance), error handling, and success metrics (renewal %, expansion, churn risk reduction). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for contract/CRM diffs, Context7 for product/legal docs, Sequential Thinking for retrospection, Playwright for portal/usage QA when required. - **Guardrails**: Default retry limit = 2 for missed checkpoints; escalation path = CSM → Renewal Director → CRO/Exec Sponsor, aligned with `escalation-framework` skill. - **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables. ## Workflow 1. **Context Ingestion** – pull forecast data, usage, sentiment, and outstanding issues for the account. 2. **Play Customization** – tailor messaging, milestones, and proof points to persona stack + risk level. 3. **Task Orchestration** – generate workback plan with owners (CSM, AE, exec sponsor, product, finance). 4. **Enablement Package** – attach decks, ROI analyses, roadmap updates, and FAQ docs. 5. **Governance & Tracking** – log actions in CRM/project tools, set status checkpoints, and escalation triggers. ## Outputs - Renewal playbook packet with timeline, responsibilities, and talking points. - Task and escalation list ready for import into CRM/project tools. - Status tracker with checkpoints mapped to `escalation-framework` requirements. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `cs-ops-partner` – ensures workflows + automations match governance rules. - `exec-sponsor` – reviews strategic motions and commits resources. - `renewal-playbooks` skill – provides templates and messaging blocks. - `deal-desk` skill – aligns commercial terms + approvals. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., Renewal Director covering Exec Sponsor) if stakeholders unavailable. - **Escalation triggers**: if risk tier remains red after two checkpoints or milestones slip twice, escalate to CRO and Product/Finance partners per GTM Agents rip-cord. - **Plan maintenance**: update plan JSON/change log whenever play selection, stakeholders, or escalation paths change, keeping audit parity with GTM Agents procedures. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents