zhongwei/gh-gtmagents-gtm-agents-plugins-referral-program-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:27 +08:00
commit bb54e4824f
12 changed files with 421 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
commands/design-referral.md Normal file
View File

@@ -0,0 +1,48 @@
---
name: design-referral
description: Produces referral program blueprint with incentives, rules, and governance.
usage: /referral-program-orchestration:design-referral --goal "pipeline" --audience "customers" --budget 25000
---
# Command: design-referral
## Inputs
- **goal** – primary objective (signups, pipeline, revenue, expansion).
- **audience** – target participants (customers, partners, employees, influencers).
- **budget** – incentive budget cap or range.
- **regions** – optional list of geo restrictions/compliance considerations.
- **timeline** – planned launch window.
### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Referral design typically uses a **diamond** (context ↔ mechanic modeling, converge into governance) or **pipeline**; document choice in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing goals, incentives, dependency graph (legal, finance, ops, partner), error handling, and success criteria (pipeline, CAC, fraud rates).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for charter diffs, Context7 for compliance + incentive benchmarks, Sequential Thinking for trade-off analysis, Playwright for prototype referral journeys.
- **Guardrails**: Default retry limit = 2 for modeling or policy failures; escalation ladder = Referral Architect → Legal/Finance → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before sign-off to confirm dependencies, approvals, deliverables.
## Workflow
1. **Context Gathering** – pull GTM targets, persona insights, legal/finance constraints.
2. **Mechanic Selection** – evaluate one-sided vs two-sided incentives, tiering, and cadence.
3. **Rules & Safeguards** – define eligibility, referral caps, fraud checks, and compliance requirements.
4. **Enablement Plan** – list assets, messaging, training, and tooling needed for launch.
5. **Measurement Framework** – connect KPIs to dashboards and define review cadence.
## Outputs
- Referral program charter (objective, mechanics, incentives, rules, KPIs).
- Stakeholder alignment deck outlining responsibilities and approvals.
- Risk log highlighting compliance/legal considerations.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `referral-architect` – leads program design and governance.
- `incentive-design` skill – structures payouts and thresholds.
- `fraud-detection` skill – recommends safeguards.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Partner Ops covering Referral Architect) when decision-makers unavailable.
- **Escalation triggers**: if compliance blockers or budget overruns appear twice, trigger GTM Agents rip-cord escalation and log remediation in plan JSON.
- **Plan maintenance**: update plan JSON/change log whenever incentives, eligibility rules, or governance cadences change.
---

48
commands/launch-program.md Normal file
View File

@@ -0,0 +1,48 @@
---
name: launch-program
description: Orchestrates referral program launch tasks, tooling, and communications.
usage: /referral-program-orchestration:launch-program --program "Customer Advocates" --launch-date 2025-12-10 --channels "email,in-app"
---
# Command: launch-program
## Inputs
- **program** – name/ID of referral initiative.
- **launch-date** – target go-live date.
- **channels** – comma-separated launch/promotion channels.
- **segments** – optional list of participant personas.
- **approvers** – optional stakeholders for gating steps.
### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Launch orchestration usually runs **pipeline** (checklist → tooling → comms → enablement → go-live). If comms + enablement run in parallel, document a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing tasks, dependencies (legal, ops, partner), error handling, and success metrics (launch readiness %, tracking accuracy, response SLAs).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for runbook diffs, Context7 for SOPs/assets, Sequential Thinking for launch reviews, Playwright for referral flows + tracking QA.
- **Guardrails**: Default retry limit = 2 for QA/tooling failures; escalation ladder = Lifecycle Ops → Referral Architect → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before locking launch date to confirm dependencies + approvals.
## Workflow
1. **Checklist Creation** – pull design charter, list tasks (tooling, creative, legal, finance) with owners.
2. **Tooling & QA** – coordinate lifecycle ops to finalize forms, tracking, reward fulfillment, and MAP workflows.
3. **Communications** – auto-generate launch emails, in-app prompts, partner kits, and support scripts.
4. **Training & Enablement** – schedule sessions for sales/CS, publish FAQs, and update help center entries.
5. **Go-live & Monitoring** – run day-of checklist, confirm tracking, enable dashboards, and log outcomes.
## Outputs
- Launch runbook with tasks, owners, due dates, and status.
- Comms kit (emails, social posts, landing pages) packaged for GTM teams.
- Monitoring plan linking dashboards, alerts, and incident response steps.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `lifecycle-ops` – drives tooling + QA.
- `partner-manager` – coordinates partner enablement and post-launch support.
- `partner-ops` skill – ensures partner workflows and approvals are documented.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Partner Manager covering Lifecycle Ops) when leads unavailable.
- **Escalation triggers**: escalate if tooling QA fails twice or compliance approvals slip; follow GTM Agents rip-cord, log remediation in plan JSON.
- **Plan maintenance**: update plan JSON/change log when tasks, owners, or channels change to keep audit-ready history.
---

49
commands/optimize-referrals.md Normal file
View File

@@ -0,0 +1,49 @@
---
name: optimize-referrals
description: Analyzes referral performance, fraud risk, and partner health to recommend improvements.
usage: /referral-program-orchestration:optimize-referrals --window 30d --detail full --dimensions "channel,partner-tier"
---
# Command: optimize-referrals
## Inputs
- **window** – analysis horizon (7d, 30d, 90d).
- **detail** – summary | full to control output length.
- **dimensions** – optional breakdowns (channel, persona, partner-tier, region).
- **experiments** – optional list of tests to evaluate.
- **alert_threshold** – optional KPI threshold for escalations.
### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- **Pattern selection**: Optimization review typically runs **pipeline** (data refresh → diagnostics → risk review → partner health → action plan). If diagnostics + risk review can run concurrently, note a **diamond** block with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing window, datasets, task IDs, dependency graph (BI, fraud, partner ops), error handling, and success metrics (conversion lift, fraud reduction, partner NPS).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for schema diffs, Context7 for referral SOPs/partner comms, Sequential Thinking for retro cadence, Playwright for offer flows or portal QA.
- **Guardrails**: Default retry limit = 2 for failed data pulls or fraud model runs; escalation ladder = Referral Architect → Partner Ops → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before distributing recommendations to confirm dependencies and approvals.
## Workflow
1. **Data Refresh** – pull referral submissions, conversions, payouts, fraud flags, and NPS per dimension.
2. **Performance Diagnostics** – inspect funnel (invites → referrals → pipeline → revenue) and incentive efficiency.
3. **Risk Review** – run fraud heuristics, identify suspicious cohorts, confirm compliance logs.
4. **Partner Health** – evaluate top/bottom partners, share-of-voice, and engagement levels.
5. **Playbook Output** – recommend experiments (incentive tweaks, messaging, partner enablement) with expected impact.
## Outputs
- Performance dashboard snapshot with annotated insights.
- Fraud/risk summary referencing `fraud-detection` skill outputs.
- Optimization backlog with owners, ETA, and projected lift.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
## Agent/Skill Invocations
- `referral-architect` – prioritizes experiments + approvals.
- `lifecycle-ops` – implements tooling or messaging changes.
- `fraud-detection` skill – validates risk findings.
- `partner-ops` skill – coordinates partner communications.
## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Lifecycle Ops covering Architect) when leads unavailable.
- **Escalation triggers**: if alert_threshold breached twice or fraud risk spikes, trigger GTM Agents rip-cord escalation and record actions in plan JSON.
- **Plan maintenance**: update plan JSON/change log whenever metrics, thresholds, or partner tiers change to maintain audit continuity.
---