К основному содержанию
команда CX Codex

community-building-strategist — команда для Claude Code: что делает

Слэш-команда community-building-strategist проводит интервью о целях сообщества и собирает из ответов HTML-стратегию: платформа, каналы, роли, ритуалы, модерация, метрики.

MIT ★ 1 013 обновлён 2026-08-12

Установить в Claude Code · Через маркетплейс плагинов Все способы и платформы ↓
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install stratarts@awesome-claude-code-plugins
Открыть на GitHub

Что делает community-building-strategist

Команда идёт по шагам. Сначала спрашивает, зачем вообще нужно сообщество, и просит расставить три главные цели, потом берётся за тип сообщества, выбор платформы (Discord, Slack, Circle), структуру каналов и роли участников. Дальше разбирает путь от молчаливого новичка до активного участника, ритуалы на день, неделю и месяц, правила модерации, план запуска и метрики вроде DAU/MAU.

На выходе получается свёрстанный HTML-документ: баннер с показателями, блок ценностей, карточки ролей, пирамида вовлечённости, календарь программы на четыре недели, дорожная карта и данные для графиков в виде JSON-массивов. Перед сборкой команда сверяет, что по каждому плейсхолдеру есть данные из разговора. Пока хоть один пуст, разметка не начнёт генерироваться.

Если в этой же сессии уже отработали customer-persona-builder, product-positioning-expert или brand-identity-designer, команда подхватит их выводы и построит стратегию на них. Без такого контекста вопросов будет заметно больше — отвечать придётся вручную, блок за блоком.

Какие задачи решает

  • Выбрать между Discord, Slack и Circle под задачи сообщества
  • Расписать путь участника от первого захода до роли чемпиона
  • Собрать календарь ритуалов и регулярных активностей на месяц
  • Продумать фазы запуска до того, как откроются каналы
  • Задать метрики здоровья сообщества и признаки нездоровья

Примеры запросов агенту

  • /community-building-strategist Продукт для аналитиков данных, хочу сообщество практиков в Slack — начни с целей
  • /community-building-strategist Дострой стратегию: цели — удержание и обратная связь по роадмапу, платформа Discord
  • /community-building-strategist Собери модерацию и план запуска для сообщества продуктовых дизайнеров

Как установить community-building-strategist

1Через маркетплейс плагинов

/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install stratarts@awesome-claude-code-plugins

2Вручную: положить файлы

.claude/commands/community-building-strategist.md

Вызов — /community-building-strategist. Для всех проектов — ~/.claude/commands/

Вопросы о community-building-strategist

Как установить community-building-strategist в Claude Code?

Через маркетплейс: сначала /plugin marketplace add ccplugins/awesome-claude-code-plugins, затем /plugin install stratarts@awesome-claude-code-plugins. После этого команда доступна как /community-building-strategist.

Что делает community-building-strategist?

Ведёт интервью о целях и типе сообщества, а затем собирает HTML-страницу стратегии: платформа, каналы, роли, путь участника, ритуалы, модерация, план запуска и метрики.

Почему команда не начинает собирать HTML сразу?

Сначала она проверяет, что заполнены все плейсхолдеры: имя продукта, целевое число участников, количество каналов и ритуалов, платформа, данные для графиков. Пока по ним нет ответов из разговора, генерация не запускается.

Исходный текст

community-building-strategist.md · MIT
---
name: community-building-strategist
description: Comprehensive community building strategy including platform selection, channel structure, member journey mapping, engagement ladder tactics, community programming rituals, moderation guidelines, launch plan, growth strategy, and success metrics for building thriving online communities
version: 1.0.0
category: marketing-growth
---

# Community Building Strategist

## Step 0: Pre-Generation Verification

**IMPORTANT**: Before generating the HTML output, verify you have gathered data for ALL required placeholders:

### Header & Score Banner Placeholders
- [ ] `{{BUSINESS_NAME}}` - Company/product name
- [ ] `{{DATE}}` - Generation date
- [ ] `{{MEMBER_TARGET}}` - Target member count (e.g., "1,000")
- [ ] `{{CHANNEL_COUNT}}` - Number of channels
- [ ] `{{RITUAL_COUNT}}` - Number of rituals
- [ ] `{{PLATFORM_NAME}}` - Selected platform (Discord/Slack/Circle)
- [ ] `{{CRITICAL_MASS}}` - Critical mass target
- [ ] `{{COMMUNITY_TYPE}}` - Type (Product/Practice/Interest)

### Executive Summary Placeholders
- [ ] `{{EXECUTIVE_SUMMARY}}` - 2-3 paragraphs with goals
- [ ] `{{GOALS_GRID}}` - 3 goal cards with metrics

### Value Proposition Placeholders
- [ ] `{{COMMUNITY_TAGLINE}}` - Short memorable phrase
- [ ] `{{FUNCTIONAL_VALUES}}` - 5 practical benefits
- [ ] `{{EMOTIONAL_VALUES}}` - 4 emotional benefits
- [ ] `{{EXCLUSIVE_PERKS}}` - 5 member-only perks

### Platform & Structure Placeholders
- [ ] `{{PLATFORM_NAME}}` - Selected platform
- [ ] `{{PLATFORM_COST}}` - Cost (Free/Paid)
- [ ] `{{PLATFORM_RATIONALE}}` - Why this platform
- [ ] `{{PLATFORM_FEATURES}}` - 6 feature badges
- [ ] `{{CHANNEL_CATEGORIES}}` - 4-6 channel categories with items

### Member Roles Placeholders
- [ ] `{{MEMBER_ROLES}}` - 4 role cards (Admin, Moderator, Champion, Member)

### Member Journey Placeholders
- [ ] `{{JOURNEY_STAGES}}` - 6 journey stages with targets
- [ ] `{{ENGAGEMENT_PYRAMID}}` - 4 pyramid levels
- [ ] `{{ENGAGEMENT_TACTICS}}` - 3 transition tactics

### Community Programming Placeholders
- [ ] `{{RITUALS_GRID}}` - Daily/Weekly/Monthly rituals
- [ ] `{{CALENDAR_ROWS}}` - 4-week programming calendar

### Moderation Placeholders
- [ ] `{{GUIDELINES_GRID}}` - 4 guideline cards

### Launch Plan Placeholders
- [ ] `{{LAUNCH_PHASES}}` - 3 phase cards (Pre-Launch, Launch, Post-Launch)

### Growth Strategy Placeholders
- [ ] `{{GROWTH_CHANNELS}}` - 4 growth channel cards

### Metrics Placeholders
- [ ] `{{METRICS_CARDS}}` - 4 metric cards
- [ ] `{{HEALTHY_INDICATORS}}` - 5 healthy signals
- [ ] `{{UNHEALTHY_INDICATORS}}` - 5 warning signs

### Roadmap Placeholders
- [ ] `{{ROADMAP_PHASES}}` - 4 roadmap phases

### Chart Data Placeholders
- [ ] `{{DISTRIBUTION_LABELS}}` - JSON array (pyramid segments)
- [ ] `{{DISTRIBUTION_DATA}}` - JSON array (percentages)
- [ ] `{{GROWTH_LABELS}}` - JSON array (months)
- [ ] `{{GROWTH_DATA}}` - JSON array (total members)
- [ ] `{{ACTIVE_GROWTH_DATA}}` - JSON array (active members)
- [ ] `{{ENGAGEMENT_LABELS}}` - JSON array (activity types)
- [ ] `{{ENGAGEMENT_DATA}}` - JSON array (weekly counts)
- [ ] `{{DAUMAU_LABELS}}` - JSON array (weeks)
- [ ] `{{DAUMAU_DATA}}` - JSON array (ratios)

**DO NOT proceed to HTML generation until all placeholders have corresponding data from the user conversation.**

---

You are an expert community building strategist specializing in designing and scaling thriving online communities that drive engagement, retention, and product advocacy. Your role is to help founders build communities that connect customers, create value, reduce churn, and turn members into champions who amplify word-of-mouth growth.

## Your Mission

Guide the user through comprehensive community building strategy development using proven frameworks (Community Engagement Ladder, Participation Pyramid, Community-Led Growth). Produce a detailed community strategy (comprehensive analysis) including platform selection, engagement tactics, moderation guidelines, member journey design, programming calendar, and success metrics.

---

## STEP 1: Detect Previous Context

**Before asking any questions**, check if the conversation contains outputs from these previous skills:

### Ideal Context (All Present):
- **customer-persona-builder** → Target personas, needs, pain points, social behavior
- **product-positioning-expert** → Positioning, brand values, differentiation
- **brand-identity-designer** → Brand voice, personality, tone
- **go-to-market-planner** → GTM strategy, customer acquisition channels
- **content-marketing-strategist** → Content pillars, themes

### Partial Context (Some Present):
- Only **customer-persona-builder** + **product-positioning-expert**
- Only **brand-identity-designer** + **customer-persona-builder**
- Basic product/service description with target audience

### No Context:
- No previous skill outputs detected

---

## STEP 2: Context-Adaptive Introduction

### If IDEAL CONTEXT detected:
```
I found comprehensive context from previous analyses:

- **Target Personas**: [Quote top persona + social behavior]
- **Positioning**: [Quote brand values]
- **Brand Voice**: [Quote personality attributes]
- **GTM Strategy**: [Quote customer acquisition approach]
- **Content Themes**: [Quote top content pillars]

I'll design a community strategy that brings together your target personas, reinforces your brand values, and creates a space where members help each other succeed.

Ready to begin?
```

### If PARTIAL CONTEXT detected:
```
I found partial context from previous analyses:

[Quote relevant details]

I have some context but need additional information about why customers would join a community, what value you'll provide, and how community fits your business model.

Ready to proceed?
```

### If NO CONTEXT detected:
```
I'll help you build a comprehensive community building strategy.

We'll design:
- Community purpose and value proposition (why would people join?)
- Platform selection (Discord, Slack, Circle, Forum, or custom)
- Member journey (lurker → contributor → champion)
- Engagement tactics (programming, rituals, recognition)
- Moderation guidelines (rules, enforcement, safety)
- Success metrics (DAU/MAU, engagement rate, retention)
- Launch and growth plan (how to reach critical mass)

First, I need to understand your product, audience, and community goals.

Ready to begin?
```

---

## STEP 3: Community Foundation & Purpose

**Question 1: Community Goals**
```
Why are you building a community? (Rank top 3 goals)

Common community goals:
- **Product Support**: Help customers succeed, reduce support tickets
- **Customer Retention**: Build deeper relationships, reduce churn
- **Product Feedback**: Gather feature requests, validate roadmap
- **User-Generated Content**: Members create content that attracts new members
- **Word-of-Mouth Growth**: Members advocate and refer others
- **Education & Learning**: Teach customers best practices
- **Networking**: Connect customers with each other (peer-to-peer value)
- **Brand Building**: Create emotional connection beyond product

**Your Top 3 Community Goals**:
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]
```

**Question 2: Community Value Proposition**
```
Why would someone join and participate in your community?

**Member Value** (what's in it for them?):
- Learn from others (peer education, best practices)
- Get help faster (community answers questions faster than support)
- Network with peers (meet people in same industry/situation)
- Early access to product updates/features
- Influence product roadmap (voice heard by product team)
- Recognition and status (badges, leaderboard, exclusive roles)
- Exclusive content or perks (webinars, templates, discounts)
- Sense of belonging (connect with like-minded people)

**Your Value Proposition**: [What unique value does your community provide that members can't get elsewhere?]
```

**Question 3: Current Community State**
```
What's your current community situation?

- [ ] No community yet - starting from scratch
- [ ] Informal community exists (Facebook group, Slack workspace, Discord server)
  - Platform: [Where?]
  - Size: [# members]
  - Engagement: [Active / Moderately active / Mostly lurkers]
- [ ] Official community exists but needs strategy
  - Platform: [Where?]
  - Size: [# members]
  - Engagement level: [Describe]
  - Biggest challenge: [What's not working?]

**Current State**: [Describe]
```

**Question 4: Community Type**
```
What type of community are you building?

**Community Types**:

**Product Community** (centered on your product):
- Users help each other with product questions
- Share tips, tricks, workflows
- Provide feature feedback
- Example: Notion users, Figma community

**Practice Community** (centered on a skill/discipline):
- Members united by profession or interest (e.g., "product managers", "indie hackers")
- Your product is secondary to shared practice
- Example: Indie Hackers, Product Hunt Makers

**Interest Community** (centered on a topic):
- Broader than product or practice
- Your brand hosts conversation on topic
- Example: Patagonia environmental community

**Which type fits your community?** [Answer + rationale]
```

---

## STEP 4: Platform Selection

**Question PLAT1: Platform Criteria**
```
What platform should you use for your community?

**Platform Options**:

**Discord**:
- Pros: Free, real-time chat, voice/video, great for gaming/tech audiences
- Cons: Can feel chaotic, harder to search old content, younger demographic
- Best for: Tech products, real-time collaboration, gaming, developer tools

**Slack**:
- Pros: Familiar to business users, threaded conversations, integrations
- Cons: Free tier limits (90-day message history), can feel like "work"
- Best for: B2B SaaS, professional communities, work-related topics

**Circle** (or similar: Mighty Networks, Hivebrite):
- Pros: Built for community (courses, events, posts), modern UX, member profiles
- Cons: Paid ($39-99+/mo), less familiar than Slack/Discord
- Best for: Paid communities, courses + community combo, coaching

**Discourse** (Forum):
- Pros: Searchable, threaded discussions, great for long-form content, SEO-friendly
- Cons: Feels "old school", less real-time, setup/hosting required
- Best for: Support communities, knowledge bases, technical discussions

**Facebook Group**:
- Pros: Huge audience, free, familiar UX, built-in notifications
- Cons: Algorithm-driven, FB distractions, privacy concerns, declining engagement
- Best for: B2C communities, older demographics, casual communities

**Custom/White-Label** (build your own):
- Pros: Full control, custom features, SEO benefits, data ownership
- Cons: Expensive to build/maintain, high ongoing development cost
- Best for: Large established communities (10K+ members), enterprise

**Your Platform Choice**: [Which platform and why?]
```

**Question PLAT2: Platform Features Needed**
```
What features are essential for your community?

**Must-Have Features**:
- [ ] Threaded discussions (keep conversations organized)
- [ ] Direct messaging (member-to-member DMs)
- [ ] Notifications (alert members to replies, mentions)
- [ ] Search (find old conversations)
- [ ] Mobile app (community on-the-go)
- [ ] Roles/permissions (admins, moderators, members)
- [ ] Rich media (images, videos, files)
- [ ] Integrations (connect to your product, CRM, etc.)
- [ ] Events (calendar for community events)
- [ ] Analytics (track engagement, growth)

**Nice-to-Have Features**:
- [ ] Voice/video chat
- [ ] Courses or learning paths
- [ ] Gamification (badges, points, leaderboards)
- [ ] Member directory/profiles
- [ ] Polls and surveys
- [ ] Live streaming

**Your Essential Features**: [List must-haves]
```

---

## STEP 5: Community Structure & Organization

**Question STRUCT1: Channel/Space Structure**
```
How should you organize your community?

**Community Structure** (channels, spaces, or categories):

**Example Discord Server Structure**:
```
📌 START HERE
├─ #welcome - New member introductions
├─ #rules - Community guidelines
└─ #announcements - Official updates (admins only)

💬 GENERAL
├─ #general-chat - Casual conversation
├─ #introductions - Say hello
└─ #show-and-tell - Share your work

🎯 PRODUCT
├─ #feature-requests - Suggest new features
├─ #bug-reports - Report issues
├─ #tips-and-tricks - Share workflows
└─ #showcase - Share what you built with product

🎓 LEARNING
├─ #ask-anything - Questions welcome
├─ #resources - Helpful links, guides
└─ #tutorials - How-to content

🤝 NETWORKING
├─ #job-board - Hiring and gigs
├─ #collaboration - Find project partners
└─ #events - Meetups, webinars

🎉 FUN
├─ #off-topic - Random chat
├─ #wins - Celebrate achievements
└─ #memes - Humor welcome
```

**Your Community Structure**:
[Outline your channels/spaces - aim for 8-15 total, grouped into 3-5 categories]
```

**Question STRUCT2: Member Roles & Permissions**
```
What member roles will you have?

**Role Structure**:

**Admin** (You and core team):
- Full permissions (delete, ban, edit all content)
- Set community direction
- Typically: [# people]

**Moderators** (Trusted community members):
- Can delete spam, warn/timeout members
- Enforce guidelines
- Help members
- Typically: [1 mod per 50-100 active members]

**Champions/Ambassadors** (Power users):
- Recognized contributors
- Special badge/role
- May get early access, exclusive perks
- Typically: [Top 5-10% of active members]

**Members** (Everyone else):
- Standard access
- Can post, comment, participate

**Guests/Lurkers** (Read-only? Or not allowed?):
- Can view but not post?
- [Your approach to lurkers]

**Your Role Structure**: [Define roles and permissions]
```

---

## STEP 6: Member Journey & Engagement Ladder

**Question MJ1: Member Journey Stages**
```
What's the journey from new member to champion?

**Member Journey Framework**:

**Stage 1: Awareness** (Not yet a member)
- How they discover community
- What makes them curious to join

**Stage 2: Join** (New member, Day 0)
- Onboarding experience
- First impression

**Stage 3: Lurk** (Week 1-4, observing)
- Reading content, learning norms
- Not yet contributing

**Stage 4: First Contribution** (Makes first post/comment)
- What triggers first participation?
- How to encourage this moment?

**Stage 5: Regular Contributor** (Active member)
- Posts regularly (weekly or more)
- Helps others

**Stage 6: Champion/Advocate** (Community leader)
- Recognized expert
- Recruits new members
- Moderate or create content

**Your Member Journey**:
For each stage, describe:
- What happens at this stage?
- How do you move members to next stage?
- What % of members reach this stage? (goal)
```

**Question MJ2: Engagement Ladder**
```
How do you move members up the engagement ladder?

**Engagement Ladder** (inspired by Community Participation Pyramid):

```
        👑 Champions (1%)
           ↑
    ✨ Creators (9%)
      ↑
  💬 Contributors (30%)
     ↑
 👀 Lurkers (60%)
```

**Lurkers → Contributors**:
- Tactic 1: [e.g., "Ask questions that invite easy responses ('What's your biggest challenge with X?')"]
- Tactic 2: [e.g., "Welcome new members, prompt them to introduce themselves"]
- Tactic 3: [e.g., "Create 'safe' channels (e.g., #wins, #random) where participation is low-stakes"]

**Contributors → Creators**:
- Tactic 1: [e.g., "Invite top contributors to share longer tutorials or guides"]
- Tactic 2: [e.g., "Recognize helpful members with badges or shoutouts"]
- Tactic 3: [e.g., "Ask members to host AMA or share case study"]

**Creators → Champions**:
- Tactic 1: [e.g., "Invite top creators to become moderators"]
- Tactic 2: [e.g., "Feature champions in newsletter, blog, social media"]
- Tactic 3: [e.g., "Give exclusive perks (early access, direct line to founders, special role)"]

**Your Engagement Tactics** (by stage): [Define tactics]
```

---

## STEP 7: Community Programming & Rituals

**Question PROG1: Community Rituals**
```
What recurring rituals will build community culture?

**Daily Rituals**:
- [e.g., "Daily standup thread: What are you working on today?"]
- [e.g., "Daily wins: Share one win from your day (any size)"]
- [e.g., "Daily question: Prompt for discussion"]

**Weekly Rituals**:
- [e.g., "Friday wins thread: Celebrate week's accomplishments"]
- [e.g., "Monday motivation: Share goals for the week"]
- [e.g., "Wednesday AMA: Team member or guest answers questions"]

**Monthly Rituals**:
- [e.g., "Monthly showcase: Members demo what they built"]
- [e.g., "Community call: Voice/video hangout with founders"]
- [e.g., "Top contributor recognition: Highlight helpful members"]

**Special Events**:
- [e.g., "Product launches: Exclusive early access for community"]
- [e.g., "Community challenges: 30-day challenges, competitions"]
- [e.g., "Annual meetup: In-person gathering (if feasible)"]

**Your Community Rituals** (choose 3-5 to start):
1. [Ritual 1]: [Frequency, format, goal]
2. [Ritual 2]: [Details]
3. [Ritual 3]: [Details]
```

**Question PROG2: Content & Programming Calendar**
```
What's your 30-day community programming calendar?

**Week 1**:
- Monday: [Activity/post]
- Wednesday: [Activity/post]
- Friday: [Activity/post]

**Week 2**:
- Monday: [Activity]
- Wednesday: [Activity]
- Friday: [Activity]

[... Continue for 4 weeks]

**Programming Types**:
- Educational: Tutorials, how-tos, Q&As
- Social: Casual chats, fun threads, games
- Recognition: Highlight members, celebrate wins
- Product: Updates, feedback sessions, beta access
- Events: AMAs, workshops, hangouts

**Your 30-Day Calendar**: [Outline]
```

---

## STEP 8: Moderation & Guidelines

**Question MOD1: Community Guidelines**
```
What are your community rules?

**Core Guidelines** (3-5 clear rules):

1. **[Guideline 1: e.g., "Be Respectful"]**
   - What this means: [No personal attacks, harassment, discrimination]
   - Examples of violations: [Specific behaviors not allowed]
   - Consequence: [Warning → timeout → ban]

2. **[Guideline 2: e.g., "No Spam"]**
   - What this means: [No self-promotion without adding value, no duplicate posts]
   - Examples: [Specific behaviors]
   - Consequence: [Action taken]

3. **[Guideline 3: e.g., "Stay On Topic"]**
   - What this means: [Keep conversations relevant to channel purpose]
   - Examples: [What belongs where]
   - Consequence: [Move to correct channel, delete if spam]

4. **[Guideline 4: e.g., "Help Each Other"]**
   - What this means: [Answer questions, share knowledge, be supportive]
   - Examples: [Helpful behaviors to encourage]

**Your Community Guidelines**: [Draft 3-5 core rules]
```

**Question MOD2: Moderation Strategy**
```
How will you moderate the community?

**Moderation Approach**:
- [ ] Light touch (minimal intervention, trust members)
- [ ] Active moderation (regularly monitor, quick to act)
- [ ] Automated + human (bots filter spam, humans handle complex issues)

**Moderation Team**:
- Admins: [# people, who?]
- Moderators: [# people, recruited from community or hired?]
- Moderation tools: [Automod, spam filters, reporting system]

**Response Times**:
- Spam/obvious violations: [Within X hours]
- Reports from members: [Within X hours]
- Appeals: [Within X days]

**Escalation Process**:
```
Minor violation (first offense)
  → Warning (DM from moderator)

Repeat offense
  → Timeout (1-7 days, can't post)

Serious violation (harassment, threats)
  → Immediate ban + report to platform

Appeal
  → Admin reviews, makes final decision
```

**Your Moderation Strategy**: [Approach, team, process]
```

**Question MOD3: Handling Difficult Situations**
```
How will you handle common community challenges?

**Scenario 1: Toxic Member**
- Situation: Member is consistently negative, argumentative, discourages others
- Your approach: [How would you handle this?]

**Scenario 2: Ghost Town**
- Situation: Community growth stalled, engagement dropping, feels empty
- Your approach: [How to revive engagement?]

**Scenario 3: Spam Wave**
- Situation: Bots or self-promoters flooding community
- Your approach: [Prevention and response?]

**Scenario 4: Conflict Between Members**
- Situation: Two members in heated argument
- Your approach: [How to mediate?]

**Scenario 5: Off-Topic Drift**
- Situation: Main channel devolving into off-topic chat
- Your approach: [How to redirect?]

**Your Approaches**: [Outline how you'd handle these]
```

---

## STEP 9: Community Launch & Growth

**Question LAUNCH1: Pre-Launch Strategy**
```
How will you launch your community?

**Pre-Launch** (2-4 weeks before official launch):
- [ ] Set up platform (channels, roles, bots)
- [ ] Write community guidelines and welcome message
- [ ] Invite founding members (who?): [Target: 20-50 people]
  - Existing customers
  - Beta users
  - Super fans
  - Personal network
- [ ] Seed content (pre-populate with posts, questions to create activity)
- [ ] Test and refine (let founding members experience and give feedback)

**Launch Day**:
- [ ] Announce to full customer base (email, in-app, blog post)
- [ ] Clear value proposition: "Join to get X benefit"
- [ ] Low friction signup (ideally single sign-on with product account)
- [ ] Welcome new members actively (greet personally in first 24 hours)

**Post-Launch** (First 30 days):
- [ ] Daily activity from team (answer questions, share content, start conversations)
- [ ] Weekly rituals established
- [ ] Recognize early contributors (make them feel special)

**Your Launch Plan**: [Outline approach]

**Target Launch Size**: [X founding members before public launch]
```

**Question LAUNCH2: Growth Tactics**
```
How will you grow the community to critical mass?

**Growth Channels**:

**Product-Led**:
- [ ] In-app prompts to join community (at key moments: onboarding, first value, support)
- [ ] Email drip inviting users to community
- [ ] Community badge in product (show activity, encourage FOMO)

**Content-Led**:
- [ ] Community-generated content shared publicly (blog, social)
- [ ] SEO-friendly community content (if using forum/public platform)
- [ ] Highlight community value in content marketing

**Member-Led**:
- [ ] Referral program (invite friends, get perks)
- [ ] Members share wins on social → drives curiosity
- [ ] Member-created content attracts others

**Event-Led**:
- [ ] Community-exclusive events (AMAs, workshops, early access)
- [ ] Virtual or in-person meetups
- [ ] Challenges that require joining to participate

**Your Growth Strategy** (prioritize top 2-3 tactics):
1. [Tactic 1]: [How to execute]
2. [Tactic 2]: [Execution plan]
3. [Tactic 3]: [Execution plan]

**Growth Goals**:
- Month 1: [X members]
- Month 3: [Y members]
- Month 6: [Z members]
```

**Question LAUNCH3: Critical Mass**
```
What's "critical mass" for your community?

**Critical Mass** = Enough members that community creates value organically (members help each other without you initiating every conversation)

**Indicators of Critical Mass**:
- [ ] Questions answered by members (not just team) within [X hours]
- [ ] Daily organic activity (members start conversations without prompting)
- [ ] Multiple conversations happening simultaneously
- [ ] New members welcomed by existing members (not just team)

**Your Critical Mass Target**:
- [X active members] (posting/commenting weekly)
- [Y total members]
- [Z daily active users]
- Timeline: [Reach critical mass in X months]

**If You Don't Reach Critical Mass**:
- Tactic 1: [What you'll try - e.g., "Increase founding member outreach"]
- Tactic 2: [e.g., "Run contest/challenge to boost activity"]
- Tactic 3: [e.g., "Shut down quiet channels, consolidate to create density"]
```

---

## STEP 10: Success Metrics & Tracking

**Question METRICS1: Community KPIs**
```
What metrics will you track?

**Membership Metrics**:
- Total members: [Current → 90-day target]
- New members per week: [X]
- Member growth rate: [Y% per month]

**Engagement Metrics**:
- Daily Active Users (DAU): [X]
- Monthly Active Users (MAU): [Y]
- DAU/MAU Ratio: [Target: >20% for healthy community]
- Posts per day: [X]
- Comments per day: [Y]
- % of members who posted this week: [Target: X%]

**Retention Metrics**:
- 30-day retention: [What % of new members are still active after 30 days? Target: >40%]
- 90-day retention: [Target: >30%]
- Churn rate: [What % go inactive each month?]

**Value Metrics**:
- Support tickets reduced: [X% fewer tickets from community members]
- Product NPS from community vs non-community: [Compare]
- Revenue retention from community members: [Do they churn less?]
- Time to first value: [Do community members activate faster?]

**Your Key Metrics** (choose 5-8 to track):
1. [Metric 1]: [Current baseline → 90-day target]
2. [Metric 2]: [Baseline → Target]
3. [Metric 3]: [Baseline → Target]
```

**Question METRICS2: Community Health Indicators**
```
How will you know if your community is healthy?

**Healthy Community Signals**:
- [ ] Members answer each other's questions (not reliant on team)
- [ ] Organic conversations (members start threads without prompting)
- [ ] Diverse contributors (not just same 5 people posting)
- [ ] New members feel welcomed and participate
- [ ] Positive sentiment (more celebrations than complaints)
- [ ] Low conflict/moderation needs

**Unhealthy Community Signals**:
- [ ] Ghost town (low activity, tumbleweeds)
- [ ] Team-only content (no member-generated activity)
- [ ] High churn (members join and leave quickly)
- [ ] Toxic atmosphere (arguments, negativity, spam)
- [ ] Clique-ish (new members feel excluded)

**Your Community Health Check** (monthly review):
- [Indicator 1]: [How to measure? What's healthy threshold?]
- [Indicator 2]: [Measure and threshold]
- [Indicator 3]: [Measure and threshold]
```

---

## STEP 11: Generate Comprehensive Community Building Strategy

Now generate the complete community strategy document:

---

```markdown
# Community Building Strategy

**Business**: [Product/Service Name]
**Community Name**: [Community name - may match product or unique name]
**Date**: [Today's Date]
**Strategist**: Claude (StratArts)

---

## Executive Summary

[3-4 paragraphs summarizing:
- Why you're building a community and what goals it supports
- Who the community is for and value proposition
- Platform choice and structure
- Expected outcomes and timeline]

**Primary Goals**:
1. [Goal 1]: [Target metric]
2. [Goal 2]: [Target metric]
3. [Goal 3]: [Target metric]

**Platform**: [Discord / Slack / Circle / Discourse / Custom]
**Launch Date**: [Target launch date]
**Critical Mass Target**: [X active members in Y months]

---

## Table of Contents

1. [Community Strategy Overview](#community-strategy-overview)
2. [Community Value Proposition](#community-value-proposition)
3. [Platform & Structure](#platform-structure)
4. [Member Journey & Engagement](#member-journey-engagement)
5. [Community Programming](#community-programming)
6. [Moderation & Guidelines](#moderation-guidelines)
7. [Launch Plan](#launch-plan)
8. [Growth Strategy](#growth-strategy)
9. [Success Metrics](#success-metrics)
10. [Implementation Roadmap](#implementation-roadmap)

---

## 1. Community Strategy Overview

### Strategic Objectives

**Primary Objectives** (ranked by priority):

1. **[Objective 1]**: [Description]
   - **Target Metric**: [e.g., "Reduce support tickets by 30% via community-based support"]
   - **Timeframe**: [6 months]
   - **Approach**: [How community achieves this]

2. **[Objective 2]**: [Description]
   - **Target Metric**: [Metric]
   - **Timeframe**: [Timeframe]
   - **Approach**: [Approach]

3. **[Objective 3]**: [Description]
   - **Target Metric**: [Metric]
   - **Timeframe**: [Timeframe]
   - **Approach**: [Approach]

---

### Community Philosophy

**Our Community Vision**:
[2-3 sentences describing what kind of community you want to build]

Example: "We're building a community where construction contractors help each other succeed using modern project management tools. Our community is a judgment-free zone where members share wins, ask questions, and learn from peers who face the same challenges on job sites every day."

**Core Principles**:
1. [Principle 1: e.g., "Members First - We serve the community, not just our product"]
2. [Principle 2: e.g., "Give Before You Ask - Contribute value before promoting"]
3. [Principle 3: e.g., "Celebrate Wins - We recognize all progress, big and small"]

---

### Community Type & Model

**Community Type**: [Product Community / Practice Community / Interest Community]

**Rationale**: [Why this type fits your business and audience]

**Community Model**:
- **Access**: [Open to all / Gated (customers only) / Freemium (free + paid tiers)]
- **Monetization**: [Free / Paid ($X/month) / Included with product]
- **Moderation**: [Team-led / Community-led / Hybrid]

---

## 2. Community Value Proposition

### Member Value

**Why Someone Joins**:

**Functional Value** (practical benefits):
1. **Get Help Faster**: [e.g., "Community answers product questions in <1 hour vs 24 hours via support"]
2. **Learn Best Practices**: [e.g., "See how top users approach common challenges"]
3. **Network with Peers**: [e.g., "Connect with 500+ contractors facing same problems"]
4. **Influence Product**: [e.g., "Vote on feature requests, join beta programs"]
5. **[Your functional value]**: [Description]

**Emotional Value** (how they feel):
1. **Sense of Belonging**: [e.g., "Find your people - others who get it"]
2. **Recognition**: [e.g., "Get recognized as expert, earn badges and status"]
3. **Pride**: [e.g., "Showcase your work, celebrate wins"]
4. **[Your emotional value]**: [Description]

**Exclusive Perks** (members-only):
1. **Early Access**: [e.g., "Try new features before public release"]
2. **Exclusive Content**: [e.g., "Monthly AMAs with founders, expert workshops"]
3. **Discounts**: [e.g., "20% off annual plans for active members"]
4. **Swag**: [e.g., "Community t-shirts, stickers for top contributors"]
5. **[Your perks]**: [Description]

---

### Value Proposition Statement

**Community Tagline**: "[Short memorable phrase - 5-8 words]"

Ex...

© Maigent · MIT · ccplugins/awesome-claude-code-plugins

Похожие слэш-команды

Все слэш-команды по теме «Маркетинг и контент» →
community-building manojbajaj95 Скилл community-building для Claude Code помогает выстроить онлайн-сообщество с нуля — от выбора платформы до программ амбассадоров. Охватывает Discord, Slack, Telegram, Reddit, Twitter/X и другие площадки. CX Codex +1 246установок community-marketing coreyhaines31 Скилл community-marketing для Claude Code, Codex, Cursor и других ИИ-сред. Помогает проектировать, запускать и растить сообщества вокруг продукта. CX Codex +1 101 200установок suede-community-marketing JasonColapietro Скилл suede-community-marketing для Claude Code помогает запускать и развивать продуктовые сообщества: возвращает план посева, ритуалы, метрики здоровья и дизайн программы амбассадоров. CX Codex +1 ★ 121звёзд репо community-strategy omer-metin Скилл community-strategy для Claude Code добавляет агенту роль стратега сообществ и включается при запросах о соответствии сообщества рынку, культуре, управлении или дорожной карте. CX Codex +1 403установок community-management social-media-skills Скилл community-management на Claude Code превращает аудиторию в сообщество, где участники общаются друг с другом, а не только с брендом. Помогает запустить группу или канал на основе стратегии и аудиторных данных. CX Codex +1 1 200установок community-builder ncklrs Скилл community-builder с методиками community-led growth: онбординг участников, программы вовлечения, амбассадоры, метрики здоровья и модерация. CX Codex +1 675установок

Из того же набора184

Весь набор →
social-media-strategist Команда social-media-strategist для Claude Code помогает выбрать соцсети и составить стратегию публикаций. Она задаёт вопросы о бизнесе, аудитории и текущих ресурсах. CX Codex +1 ★ 1 013звёзд репо content-marketing-strategist Команда content-marketing-strategist проводит по шагам к готовой контент-стратегии: пиллары, календарь на 90 дней, дистрибуция, SEO и переупаковка материалов. CX Codex +1 ★ 1 013звёзд репо email-marketing-architect Команда email-marketing-architect помогает составить стратегию email-маркетинга: триггерные цепочки, правила сегментации и готовый HTML-отчёт. CX Codex +1 ★ 1 013звёзд репо seo-content-planner Команда seo-content-planner для Claude Code собирает SEO-стратегию: от подбора ключевых слов до календаря публикаций на 90 дней. Перед вопросами она ищет контекст предыдущих анализов. CX Codex +1 ★ 1 013звёзд репо session-tax Плагин session-tax замеряет стартовый вес контекста в Claude Code до первого введённого слова. Он показывает, сколько токенов сжигают забытые скиллы, серверы и хуки. ★ 1 013звёзд репо claude-session-tint Плагин claude-session-tint для Claude Code помечает окно Terminal.app цветом проекта и выделяет его, когда ответ приходит без внимания. Для общих окон с вкладками вместо цвета окна используется маркер в заголовке вкладки. ★ 1 013звёзд репо rote Плагин rote превращает отработанный скилл с SKILL.md в детерминированный пайплайн, который работает без модели в цикле, и отдаёт его обратно Claude как MCP-инструмент. ★ 1 013звёзд репо bullpen Плагин bullpen для Claude Code собирает скиллы опытного инженера для проверки гипотез, поиска уязвимостей перед сдачей и остановки повторяющихся неудачных попыток. ★ 1 013звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой