plan-community-calendar — Claude Code command: event calendar
plan-community-calendar builds a community programming calendar spanning 8 weeks or a quarter, with themes, formats, owners and dependencies.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-community-calendar.mdWhat plan-community-calendar does
The command pulls engagement data, maps themes to goals (activation, adoption, advocacy), and distributes events, AMAs, content drops, and spotlights across channels (forum, Slack, Discord, webinars). Output includes a table with dates, owners and dependencies, an asset and promo checklist with deadlines, and a risk log flagging capacity or approval gaps.
The command saves a plan to .claude/plans/plan-<timestamp>.json with a dependency graph (hosts, moderators, asset teams), retry limit = 2, and escalation ladder (Community Lead → Marketing/CS → Exec sponsor). If capacity gaps or moderation risks surface twice, escalation goes to a cross-functional steering committee.
What it helps with
- build a community event calendar for a quarter with themes and owners
- distribute content and AMAs across channels (forum, Slack, webinars)
- map themes to activation and adoption goals
- get an asset and promo checklist with due dates
- record a dependency graph and escalation chain
Example prompts for the agent
- Build an 8-week community calendar for
forum,events,slackwith themesproduct,customer-stories:/community-orchestration:plan-community-calendar --window 8weeks --channels "forum,events,slack" --themes "product,customer-stories" - Create a quarterly calendar for forum and Discord focused on activation:
/community-orchestration:plan-community-calendar --window quarter --channels "forum,discord" --themes "activation" - Plan events for 8 weeks tied to a product launch:
/community-orchestration:plan-community-calendar --window 8weeks --channels "events,webinar" --dependencies "product-launch-Q2"
How to install plan-community-calendar
Manually: put the files in place
.claude/commands/plan-community-calendar.mdCall it with /plan-community-calendar. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-community-calendar.mdCall it with /prompts:plan-community-calendar. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-community-calendar.prompt.mdManually: put the files in place
.gemini/commands/plan-community-calendar.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-community-calendar
How to install plan-community-calendar in Claude Code?
Place the file .claude/commands/plan-community-calendar.md in your project.
What does plan-community-calendar do?
The command builds a community event calendar with themes, channels, owners and dependencies, outputs an asset checklist, a risk log, and a plan JSON for audit.
What channels can I specify in --channels?
Comma-separated list: forum, Slack, Discord, events, webinar, newsletter. The command distributes programming across these surfaces with formats and owners.
Source text
plan-community-calendar.md · Apache-2.0
--- name: plan-community-calendar description: Builds a rolling community programming calendar with themes, formats, and owners. usage: /community-orchestration:plan-community-calendar --window 8weeks --channels "forum,events,slack" --themes "product,customer-stories" --- # Command: plan-community-calendar ## Inputs - **window** – planning horizon (e.g., 8weeks, quarter). - **channels** – comma-separated community surfaces (forum, Slack, Discord, events, webinar, newsletter). - **themes** – optional list of focus themes or series. - **audiences** – optional persona/segment filters. - **dependencies** – optional notes on launches, campaigns, or partner tie-ins. ### GTM Agents Pattern & Plan Checklist > Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Community calendar planning typically runs **pipeline** (signals → themes → programming → resources → publishing). If programming segments (e.g., events vs async drops) run in parallel, capture a **diamond** segment with merge gate in the plan header. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing window, channels, task IDs, dependency graph (hosts, moderators, asset teams), error handling, and success metrics (attendance, engagement %, advocacy contributions). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset/promo diffs, Context7 for playbooks/guidelines, Sequential Thinking for governance/check-in cadence, Playwright for testing community microsites or forms if needed. - **Guardrails**: Default retry limit = 2 for resource shortages or tooling failures; 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. **Signal Review** – pull engagement data, VOC insights, and upcoming GTM milestones. 2. **Theme Mapping** – align themes to goals (activation, adoption, advocacy) and persona interests. 3. **Programming Mix** – schedule events, AMAs, content drops, and spotlights with owners + formats. 4. **Resource Checklist** – detail required assets, hosts, moderators, and promo timelines. 5. **Publishing Packet** – output calendar plus reminders/automation hooks for each touch. ## Outputs - Calendar table (date, theme, channel, format, owner, CTA, dependencies). - Asset + promotion checklist with due dates. - Risk log flagging capacity or approval gaps. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `community-lead` – sets strategy and approvals. - `community-ops` skill – ensures workflows and tooling readiness. - `community-analyst` – provides data context for theme prioritization. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., Community Ops covering Community Lead) when decision-makers unavailable. - **Escalation triggers**: if capacity gaps or moderation risks appear twice in planning reviews, escalate to cross-functional steering committee per GTM Agents rip-cord. - **Plan maintenance**: update plan JSON/change log when themes, channels, or dependencies change so audit trail matches GTM Agents standards. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents