Design Community Strategy

Creates multi-channel community strategy with personas, programming, and KPI plan.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Command: design-community-strategy

Inputs

  • personas – comma-separated member segments (builder, admin, exec, partner, champion).
  • objectives – adoption | advocacy | retention | research | expansion (multi-select via comma list).
  • horizon – time window for planning (quarter, half, year).
  • format – deck | memo | workspace.
  • constraints – budget, tooling, or compliance notes.

Workflow

  1. Insight Review – pull latest product, GTM, and customer signals to anchor priorities.
  2. Persona Journey Mapping – define value exchanges, needs, and hero moments per persona.
  3. Programming Blueprint – outline channels, cadences, content pillars, and staffing requirements.
  4. Measurement Architecture – map KPIs, dashboards, and attribution to business outcomes.
  5. Enablement & Governance – document owners, councils, escalation paths, and tooling stack.

Outputs

  • Community strategy deck/memo with objectives, personas, and programming roadmap.
  • KPI + instrumentation plan tied to adoption, advocacy, or revenue impact.
  • Stakeholder alignment summary with decisions, risks, and next steps.

Agent/Skill Invocations

  • community-ecosystem-strategist – leads strategy synthesis and stakeholder management.
  • community-operations-lead – validates operational feasibility + tooling.
  • community-program-matrix skill – structures programming calendar.
  • community-kpi-dashboard skill – defines measurement system.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0