Skip to main content
command CX Codex

run-launch — Claude Code command for launch planning

The run-launch command builds a launch execution plan with a timeline, communications, monitoring, and go/no-go gates. Use it to coordinate channel work and launch-day operations.

Apache-2.0 ★ 450 updated 2026-04-03

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

What run-launch does

run-launch maps a product launch’s critical path and owners, then outlines internal and external communications, telemetry, and go/no-go checks. It also plans launch-day standups, escalation, and backlog triage. The output includes a readiness checklist and a monitoring plan.

The command structures the work as a sequence or as parallel channel streams when those workstreams can proceed together. It saves a JSON plan under .claude/plans, covering stages, agent assignments, dependencies, and success criteria. The plan also includes retry and escalation procedures. Failed gates get 2 attempts by default; if KPI guardrails are breached again, the rollback path is triggered and the Exec Sponsor is notified.

What it helps with

  • map launch milestones and assign owners
  • coordinate press, blog, and customer communications
  • set go/no-go checks and document rollback triggers
  • plan monitoring with alert thresholds

Example prompts for the agent

  • Create a 14-day launch plan for AI Copilot across email, press, and webinars: /product-launch-orchestration:run-launch --product "AI Copilot" --window 14d --channels "email,press,webinars"
  • Build the AI Copilot launch plan with a feature flag, pricing, and legal approval as dependencies: `/product-launch-orchestration:run-launch --product "AI Copilot" --window 14d --channels "email,press,webinars" --dependencies "feature flag,pricing,legal approval"`

How to install run-launch

Manually: put the files in place

.claude/commands/run-launch.md

Call it with /run-launch. For all projects use ~/.claude/commands/

Questions about run-launch

How do I install run-launch in Claude Code?

Save the command file at .claude/commands/run-launch.md.

What does run-launch do?

It creates a launch execution plan covering stages, communications, monitoring, and go/no-go checks. It also stores a JSON plan under .claude/plans.

How does run-launch handle parallel channel work?

It can structure the plan as parallel streams when channel work can happen concurrently, and records the selected pattern in the plan header.

Source text

run-launch.md · Apache-2.0
---
name: run-launch
description: Creates launch execution runbook covering timeline, comms, instrumentation, and go/no-go gates.
usage: /product-launch-orchestration:run-launch --product "AI Copilot" --window 14d --channels "email,press,webinars"
---

# Command: run-launch

## Inputs
- **product** – launch identifier.
- **window** – time horizon for execution (e.g., 14d, 30d).
- **channels** – comma-separated channels/workstreams.
- **dependencies** – optional gating items (feature flag, pricing, legal approval).
- **alerts** – optional monitoring thresholds (error rate, adoption, PR sentiment).

### GTM Agents Pattern & Plan Checklist
> Inspired by GTM Agents orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Start with **pipeline** (timeline → comms → instrumentation → gates → command center). Use **diamond** when channel workstreams can run in parallel; note selection in plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, stages, parallel groups, agent assignments, context passing (e.g., feature readiness), error handling, and success criteria (launch KPIs).
- **Tool hooks**: Reference `docs/gtm-essentials.md` (Serena for doc/code patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for pre-launch QA).
- **Guardrails**: Define retry strategy (default 2 attempts) and escalation ladder (Launch Director → Product Marketing Lead → CSO) for failed gates.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, and deliverables.

## Workflow
1. **Timeline Build** – map critical path (code freeze, press embargo, enablement, GA) with owners.
2. **Communication Plan** – outline internal + external comms (press, blog, email, social, CS updates).
3. **Instrumentation & Monitoring** – confirm telemetry, dashboards, alerting, and logging.
4. **Go/No-Go Gates** – document readiness checklist, fallback plans, rollback triggers, decision authority.
5. **Launch-Day Command Center** – schedule standups, escalation tree, backlog triage process.

## Outputs
- Launch execution runbook (timeline, tasks, owners, dependencies).
- Go/no-go checklist + approval matrix.
- Monitoring plan with dashboard links and alert thresholds.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `launch-director` – orchestrates execution + governance.
- `workstream-lead` – ensures deliverables per channel.
- `war-room-ops` skill – defines command center rituals.

## GTM Agents Safeguards
- **Fallback agents**: document substitutions (e.g., Workstream Lead covering enablement) when specialists unavailable.
- **Escalation triggers**: if launch KPIs (error rate, adoption, sentiment) breach guardrails twice within 24h, execute rollback path and notify Exec Sponsor per war-room ops skill.
- **Plan maintenance**: revise plan JSON whenever dependencies, owners, or gates change; log updates in status packets.

---

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
plan-loyalty plan-loyalty generates a loyalty program blueprint with tier structures, customer incentives, and lifecycle triggers within a set budget. CX Codex +1 ★ 450repo stars manage-production The manage-production command turns a campaign and its assets into a production tracker with owners, review steps, and QA. Use it to plan work across several deliverables. CX Codex +1 ★ 450repo stars design-referral design-referral is a Claude Code command that designs referral programs with incentives, rules, and governance, producing a charter, stakeholder deck, and risk log. CX Codex +1 ★ 450repo stars design-nurture design-nurture builds multi-stage nurture journey blueprints with audience segmentation, triggers, and a content plan. Useful for planning lifecycle marketing and RevOps campaigns. CX Codex +1 ★ 450repo stars build-model The build-model command builds a data modeling plan: transforms, tests, deployment schedule and dependencies for analytics use cases. CX Codex +1 ★ 450repo stars monitor-sla monitor-sla tracks MQL to SQL SLA compliance, highlights routing bottlenecks, and suggests corrective steps across marketing and sales pipelines. CX Codex +1 ★ 450repo stars ship-dashboards ship-dashboards builds a dashboard launch plan covering visualization, publishing, user enablement, and monitoring. Use it to coordinate the rollout and define what to track afterward. CX Codex +1 ★ 450repo stars launch-program launch-program takes a referral program from task checklist through tooling, launch comms and training to a monitored go-live day. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open