design-community-strategy — Claude Code command: install
design-community-strategy is a Claude Code command that builds a community plan with personas, programming, and KPIs. It takes objectives such as adoption or retention.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/design-community-strategy.mdWhat design-community-strategy does
The design-community-strategy command turns selected personas, objectives, planning horizon, and output format into a community strategy. It reviews product, GTM, and customer signals, maps each persona's journey, then lays out channels, cadence, content pillars, and staffing needs.
The result can be a deck, memo, or workspace with a programming roadmap, KPI and instrumentation plan, and a stakeholder summary covering decisions, risks, and next steps. The constraints input carries budget, tooling, or compliance limits. The workflow can also call community-ecosystem-strategist, community-operations-lead, community-program-matrix, and community-kpi-dashboard.
What it helps with
- build a community strategy around member segments
- connect community programs to adoption, advocacy, retention, research, or expansion
- map channels, cadence, content pillars, and staffing needs
- define KPIs, dashboards, and attribution
- package decisions, risks, and next steps for stakeholders
Example prompts for the agent
- Run
/community-building:design-community-strategy --personas builder,leader --objectives adoption,advocacy --horizon 2q --format deckto create the community strategy. - Create a
memoforadmin,partnerpersonas withretention,researchobjectives across ahalfplanning horizon. - Build a
workspacethat includes the program channels, cadence, and KPIs while accounting for budget and tooling constraints.
How to install design-community-strategy
Manually: put the files in place
.claude/commands/design-community-strategy.mdCall it with /design-community-strategy. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/design-community-strategy.mdCall it with /prompts:design-community-strategy. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/design-community-strategy.prompt.mdManually: put the files in place
.gemini/commands/design-community-strategy.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about design-community-strategy
How do I install design-community-strategy in Claude Code?
Place the command file at .claude/commands/design-community-strategy.md.
What does design-community-strategy do?
It develops a community strategy by mapping personas and their journeys, planning channels and programs, tying KPIs to business outcomes, and preparing a stakeholder summary.
Which inputs does design-community-strategy accept?
It accepts personas, objectives, horizon, format, and constraints. The output format can be deck, memo, or workspace; objectives include adoption, advocacy, retention, research, and expansion.
Source text
design-community-strategy.md · Apache-2.0
--- name: design-community-strategy description: Creates multi-channel community strategy with personas, programming, and KPI plan. usage: /community-building:design-community-strategy --personas builder,leader --objectives adoption,advocacy --horizon 2q --format deck --- # 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. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents