zhongwei/gh-gtmagents-gtm-agents-plugins-renewal-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:29 +08:00
commit cb5d37da81
12 changed files with 424 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
commands/forecast-renewals.md Normal file
View File

@@ -0,0 +1,48 @@
---
name: forecast-renewals
description: Builds segmented renewal forecasts with health signals, variance commentary, and executive-ready views.
usage: /renewal-orchestration:forecast-renewals --window 90d --segment enterprise --detail full
---
# Command: forecast-renewals
## Inputs
- **window** – time horizon (30d, 60d, 90d, quarter) to include in the forecast.
- **segment** – optional filters (enterprise, midmarket, smb, region, vertical).
- **detail** – summary | full (controls depth of commentary and tables).
- **include-expansion** – true/false toggle to incorporate upsell scenarios.
- **confidence-threshold** – percentage for highlighting low-confidence projections.
### GTM Agents Pattern & Plan Checklist
> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Forecast builds usually run **pipeline** (data → segmentation → scenarios → commentary → packaging). If segmentation + scenario modeling can parallelize, note a **diamond** segment and merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, filters, task IDs, parallel groups, dependency graph (CS Ops, Finance, Product), error handling, and success metrics (forecast accuracy, coverage %, confidence spread).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for data model diffs, Context7 for product/support doc pulls, Sequential Thinking for scenario retros, Playwright for dashboard QA if embedded.
- **Guardrails**: Default retry limit = 2 for failed data pulls or scenario jobs; escalation ladder = CS Ops Partner → Renewal Director → Finance lead.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.
## Workflow
1. **Data Pull** – combine ARR, contract terms, product usage, CS health, support tickets, and sentiment data.
2. **Segmentation** – bucket accounts by tier, segment, and renewal phase; calculate coverage ratios.
3. **Scenario Modeling** – run base, upside, downside scenarios with expansion overlays.
4. **Variance Commentary** – note drivers (product adoption, exec engagement, risk flags) per segment.
5. **Package Deliverables** – produce dashboards + slides for CS leadership and finance.
## Outputs
- Renewal forecast table with ARR, NRR, churn %, and confidence per segment.
- Commentary deck with drivers, blockers, and next steps.
- Data extract for RevOps/finance to ingest into planning tools.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `renewal-director` – validates scenario assumptions and narratives.
- `cs-ops-partner` – ensures data integrity + automation hooks.
- `renewal-playbooks` skill – maps forecast insights to plays.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Exec Sponsor covering Renewal Director commentary) when specialists unavailable.
- **Escalation triggers**: if accuracy or confidence guardrails fall below thresholds twice in a row, escalate to Renewal Director + Finance leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever segments, scenario assumptions, or deliverables change to maintain GTM Agents audit parity.
---

49
commands/orchestrate-renewal-play.md Normal file
View File

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

49
commands/run-retro.md Normal file
View File

@@ -0,0 +1,49 @@
---
name: run-retro
description: Facilitates structured retrospectives after renewal cycles to capture insights, update playbooks, and improve forecasting.
usage: /renewal-orchestration:run-retro --segment enterprise --window quarter --include-churn true
---
# Command: run-retro
## Inputs
- **segment** – optional filter (enterprise, growth, scale) for the retro scope.
- **window** – time range (month, quarter, rolling-90d).
- **include-churn** – true/false toggle to include churned accounts alongside renewals.
- **dimensions** – optional grouping (cs-owner, product, geo, persona).
- **depth** – summary | workshop (adds facilitation guides + templates).
### GTM Agents Pattern & Plan Checklist
> Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Retros typically follow **pipeline** (data → analysis → insights → action planning → documentation). If insight synthesis + action planning can run in parallel (workshop mode), log a **diamond** segment with merge gate.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, scope, task IDs, parallel groups, dependencies (CS Ops, Product, Finance), error handling, and success metrics (closed-loop actions %, renewal uplift, blocker removal).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for pulling historical plan diffs, Context7 for product/support notes, Sequential Thinking for facilitation prompts, Playwright for verifying embedded dashboards if used.
- **Guardrails**: Default retry limit = 2 for data pulls or workshop sync failures; escalation ladder = Renewal Director → CS Ops Partner → Exec Sponsor.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm facilitation resources, dependencies, deliverables.
## Workflow
1. **Data Compilation** – aggregate deal outcomes, ARR deltas, health trends, product usage shifts, and qualitative notes.
2. **Pattern Analysis** – bucket learnings by reason codes, plays applied, executive involvement, and pricing.
3. **Insight Synthesis** – highlight leading indicators, blockers, and emerging opportunities.
4. **Action Planning** – assign remediation owners, timeline, and metrics for follow-up workstreams.
5. **Documentation** – publish retro deck + database entries for ongoing knowledge base.
## Outputs
- Retro report summarizing metrics, insights, and improvement themes.
- Action tracker with owners, due dates, and success criteria.
- Template slides + transcripts for sharing across CS, product, finance leadership.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `renewal-director` – sponsors session and finalizes recommendations.
- `cs-ops-partner` – compiles data and action tracker.
- `renewal-playbooks` skill – integrates learnings into new plays.
- `deal-desk` skill – informs pricing/process adjustments.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Exec Sponsor covering Renewal Director) when facilitators unavailable.
- **Escalation triggers**: if critical blockers repeat across two retros or action items stall beyond SLA, escalate to CRO + Product leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log when retro scope, owners, or follow-up workstreams change to maintain GTM Agents audit parity.
---