Skip to main content
command CX Codex

run-community-event — Claude Code command for event planning

run-community-event is a Claude Code command that drafts an agenda, moderation plan, and follow-up tasks for a community session or livestream.

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-community-event.md
Open on GitHub

What run-community-event does

The command assembles a brief, then drafts a timed agenda with speaker prompts, audience engagement points, and calls to action. It also lays out backstage roles, chat moderation guidance, promotion and reminders, and follow-up work such as handling the recording, notes, and support cases.

Outputs include an event runbook, a moderation worksheet, and tasks with owners and due dates. Event details and dependencies go into .claude/plans/plan-<timestamp>.json. Tool failures or host changes have a retry limit of 2, and incidents follow an escalation path. Serena, Context7, Sequential Thinking, and Playwright are referenced for specific prep and QA tasks.

What it helps with

  • draft a timed agenda with speaker prompts
  • assign moderation roles and escalation steps
  • prepare event promotion and reminder copy
  • turn post-event follow-up into owned tasks with due dates
  • record event dependencies and metrics in a JSON plan

Example prompts for the agent

  • Plan a Product AMA for 2025-12-05 with PM and CSM as hosts in livestream format: /community-orchestration:run-community-event
  • Draft a roundtable agenda, assign moderation roles, and include a response plan for failures.
  • Prepare event announcements and reminders, then create the post-session task list.

How to install run-community-event

Manually: put the files in place

.claude/commands/run-community-event.md

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

Questions about run-community-event

How do I install run-community-event in Claude Code?

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

What does run-community-event do?

It prepares an agenda, moderation guidance, promotion materials, and follow-up tasks for a community event or live session. It also stores event details in a JSON plan.

What details should I provide?

Give the event name, date, hosts, and format, such as a livestream or roundtable. Audience and goals, including KPIs, are optional inputs.

Source text

run-community-event.md · Apache-2.0
---
name: run-community-event
description: Generates run of show, moderation plan, and follow-up tasks for community events or live sessions.
usage: /community-orchestration:run-community-event --event "Product AMA" --date 2025-12-05 --hosts "PM,CSM" --format livestream
---

# Command: run-community-event

## Inputs
- **event** – name or theme of the session.
- **date** – scheduled date/time (ISO or natural language).
- **hosts** – comma-separated speakers/moderators.
- **format** – webinar | livestream | roundtable | in-person | async.
- **audience** – optional persona/community segment.
- **goals** – optional KPIs (registrations, NPS, product adoption prompt).

### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Live event orchestration generally runs **pipeline** (brief → run-of-show → moderation → promotion → follow-up). If moderation + promotion can run in parallel, document a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing event details, task IDs, dependency graph (hosts, ops, tooling, accessibility), error handling, and success metrics (attendance, engagement rate, CSAT/NPS).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for script/asset diffs, Context7 for event SOPs, Sequential Thinking for pre/post-mortem cadence, Playwright for registration/stream QA if needed.
- **Guardrails**: Default retry limit = 2 for tooling failures or host changes; escalation ladder = Community Lead → Marketing/CS leadership → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables.

## Workflow
1. **Brief Assembly** – capture objectives, audience, and success metrics; pull relevant insights/content.
2. **Run of Show** – outline agenda, time stamps, speaker prompts, engagement moments, and CTAs.
3. **Moderation & Ops** – assign backstage roles, chat moderation guidelines, accessibility needs, and failovers.
4. **Promotion & Reminders** – auto-generate promo copy, schedule reminders, and update community calendar.
5. **Follow-up Plan** – create recap checklist (recording, notes, action items, support cases) and measurement hooks.

## Outputs
- Event runbook (agenda, host responsibilities, tech setup, contingency plan).
- Moderation worksheet with escalation triggers and response templates.
- Follow-up task list tied to owners and due dates.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `community-lead` – approves agenda + goals.
- `community-moderator` – executes moderation plan.
- `community-ops` skill – ensures tooling + workflows are ready.
- `escalation` skill – provides incident handling guidance.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Moderator covering Community Lead) when hosts unavailable.
- **Escalation triggers**: if incidents breach guardrails (e.g., harassment, platform failure) escalate immediately per GTM Agents rip-cord; log remediation in plan JSON.
- **Plan maintenance**: update plan JSON/change log when hosts, formats, or tooling stack change so audit trail mirrors GTM Agents procedures.

---

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

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
run-survey run-survey orchestrates customer surveys with target sampling, structured question banks, and distribution steps. CX Codex +1 ★ 450repo stars configure-rules The configure-rules command takes personalization rules through data checks, decision setup, variant mapping, QA, and deployment. Use it to prepare changes for web and in-app channels. CX Codex +1 ★ 450repo stars forecast-renewals forecast-renewals — a command that builds segmented renewal forecasts with account health signals, variance analysis, and executive reporting. Combines ARR, NRR, and risk data into a single view. CX Codex +1 ★ 450repo stars experiment-design-kit experiment-design-kit structures product and growth hypotheses into test briefs with guardrails, variant catalogs, and rollback plans. CX Codex +1 ★ 450repo stars cold-email-personalization cold-email-personalization turns a prospect brief into a cold email and a follow-up series: research first, a 60-120 word draft, then a scored QA pass. CX Codex +1 ★ 450repo stars run-retro run-retro orchestrates renewal cycle retrospectives to analyze ARR shifts, review churn patterns, and generate action trackers. CX Codex +1 ★ 450repo stars trigger-plays trigger-plays is a Claude Code command that starts multi-channel campaigns from live signals and checks suppression rules. It tracks SLA status and campaign results. CX Codex +1 ★ 450repo stars orchestrate-renewal-play 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. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open