launch-program · gtmagents, referral-program-orchestration — Claude Code command: launch a referral program
launch-program takes a referral program from task checklist through tooling, launch comms and training to a monitored go-live day.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/launch-program.mdWhat launch-program does
launch-program runs a referral launch as a sequence. It pulls the design charter into a task list with owners in tooling, creative, legal and finance, then lines up forms, tracking and reward fulfilment. Next comes the comms: launch emails, in-app prompts, partner kits, support scripts, plus training sessions for sales and CS and updated help center entries.
The command orchestrates rather than executes. It calls the lifecycle-ops and partner-manager agents and the partner-ops skill. Each pass writes .claude/plans/plan-<timestamp>.json, which doubles as the audit trail when tasks, owners or channels shift.
QA and tooling failures get two retries before the escalation ladder kicks in: Lifecycle Ops → Referral Architect → Exec sponsor. The tool stack comes from docs/gtm-essentials.md, and the dependency and approval review before a launch date is locked comes from docs/usage-guide.md. Both files need to be in the repo first, otherwise the review has nothing to run against.
What it helps with
- build a launch checklist with owners and due dates
- draft launch emails, in-app prompts and support scripts
- confirm referral tracking and reward fulfilment before go-live
- set an escalation path when tooling QA fails twice
- schedule sales and CS training ahead of launch day
Example prompts for the agent
- Run
/referral-program-orchestration:launch-programfor the Customer Advocates program, launch date 2025-12-10, channelsemail,in-app. - Add participant segments and approvers to the plan, then check dependencies against
docs/usage-guide.md. - Package the comms kit: emails, in-app prompts and support scripts.
How to install launch-program
Manually: put the files in place
.claude/commands/launch-program.mdCall it with /launch-program. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/launch-program.mdCall it with /prompts:launch-program. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/launch-program.prompt.mdManually: put the files in place
.gemini/commands/launch-program.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about launch-program
How do I install launch-program in Claude Code?
Place the command file at .claude/commands/launch-program.md. The documented call carries the plugin namespace: /referral-program-orchestration:launch-program.
What does launch-program do?
It drives a referral launch through five stages: checklist, tooling and QA, communications, enablement, then go-live and monitoring. Outputs include a runbook, a comms kit, a monitoring plan and a plan JSON under .claude/plans.
Which agents does it call?
lifecycle-ops handles tooling and QA, partner-manager covers partner enablement and post-launch support, and the partner-ops skill records partner workflows and approvals.
Source text
launch-program.md · Apache-2.0
--- 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. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents
Similar slash commands
All slash commands for Marketing and content →launch-program by other authors comes first.