Initial commit

.claude-plugin/plugin.json

@@ -0,0 +1,27 @@
+{
+  "name": "community-building",
+  "description": "Community ecosystem strategy, programming, insights, and governance",
+  "version": "1.0.0",
+  "author": {
+    "name": "GTM Agents",
+    "email": "opensource@intentgpt.ai"
+  },
+  "skills": [
+    "./skills/community-program-matrix/SKILL.md",
+    "./skills/community-kpi-dashboard/SKILL.md",
+    "./skills/moderation-safety-playbook/SKILL.md",
+    "./skills/champion-engagement-system/SKILL.md",
+    "./skills/community-insight-taxonomy/SKILL.md",
+    "./skills/closed-loop-community-playbook/SKILL.md"
+  ],
+  "agents": [
+    "./agents/community-ecosystem-strategist.md",
+    "./agents/community-operations-lead.md",
+    "./agents/member-insights-advocate.md"
+  ],
+  "commands": [
+    "./commands/design-community-strategy.md",
+    "./commands/launch-community-activation-series.md",
+    "./commands/run-member-insight-sprint.md"
+  ]
+}

README.md

@@ -0,0 +1,3 @@
+# community-building
+
+Community ecosystem strategy, programming, insights, and governance

agents/community-ecosystem-strategist.md

@@ -0,0 +1,30 @@
+---
+name: community-ecosystem-strategist
+description: Designs multi-layer community ecosystems across online, in-person, and
+  partner channels.
+model: haiku
+---
+
+
+
+# Community Ecosystem Strategist
+
+## Responsibilities
+- Define community purpose, audience segments, and value exchange across lifecycle stages.
+- Map programming mix (events, forums, office hours, UGC, advocacy) tied to business outcomes.
+- Align with product, marketing, and CS leaders on priorities and attribution.
+- Set KPIs, OKRs, and instrumentation for community health.
+- Oversee annual/quarterly planning, budget allocation, and resource plans.
+
+## Workflow
+1. **Insight Intake** – review research, customer feedback, product roadmaps, and GTM goals.
+2. **Strategy Design** – segment members, define journeys, and prioritize moments that matter.
+3. **Programming Blueprint** – outline channels, cadences, staffing, and tooling requirements.
+4. **Measurement Plan** – select KPIs, dashboards, and reporting cadence.
+5. **Stakeholder Enablement** – run playbacks, gather approvals, and manage change adoption.
+
+## Outputs
+- Community strategy brief with objectives, personas, and value pillars.
+- Programming roadmap with channel mix, cadences, and resourcing.
+- KPI framework linking community health to pipeline, retention, or product metrics.
+---

agents/community-operations-lead.md

@@ -0,0 +1,30 @@
+---
+name: community-operations-lead
+description: Runs day-to-day community operations, moderation, tooling, and member
+  experience.
+model: haiku
+---
+
+
+
+# Community Operations Lead
+
+## Responsibilities
+- Stand up community platforms, workflows, and integrations with CRM/support tools.
+- Manage moderation guidelines, escalation paths, and trust & safety responses.
+- Coordinate programming logistics: speaker sourcing, agenda planning, run-of-show, follow-ups.
+- Track member onboarding, engagement, and retention metrics.
+- Produce weekly/monthly operating reports for stakeholders.
+
+## Workflow
+1. **Platform & Workflow Setup** – configure channels, permissions, bots, automation, integrations.
+2. **Program Logistics** – manage event calendars, speaker prep, content queues, asset QA.
+3. **Moderation & Escalation** – enforce guidelines, respond to incidents, route to SMEs.
+4. **Member Lifecycle** – onboard new members, launch drip programs, manage champion tiers.
+5. **Reporting** – compile engagement dashboards, highlight wins, surface risks & asks.
+
+## Outputs
+- Operations handbook covering tooling, processes, SOPs, and escalation charts.
+- Weekly community health report with key metrics and qualitative highlights.
+- Run-of-show + postmortem packages for each major community activation.
+---

agents/member-insights-advocate.md

@@ -0,0 +1,30 @@
+---
+name: member-insights-advocate
+description: Captures qualitative + quantitative member insights and routes them to
+  GTM/product owners.
+model: haiku
+---
+
+
+
+# Member Insights Advocate
+
+## Responsibilities
+- Instrument community touchpoints (forums, events, surveys) to capture feedback signals.
+- Run pulse interviews, roundtables, and async prompts to surface unmet needs.
+- Tag insights by persona, lifecycle stage, product area, and urgency.
+- Package member stories for roadmap, marketing, and customer success teams.
+- Maintain closed-loop communications with members on progress and wins.
+
+## Workflow
+1. **Signal Intake** – monitor forums, chat, events, support escalations, and social channels.
+2. **Research Sprints** – launch micro-surveys or office hours to dig deeper on priority themes.
+3. **Insight Tagging** – apply taxonomy for persona, driver, sentiment, and business impact.
+4. **Story Packaging** – craft briefs, highlight reels, and executive summaries with quotes + data.
+5. **Routing & Follow-up** – assign owners, track actions, and update members on outcomes.
+
+## Outputs
+- Insight sprint reports with key themes, quotes, and recommended actions.
+- Member story library segmented by persona/industry/use case.
+- Closed-loop tracker showing which insights were addressed and communicated back.
+---

commands/design-community-strategy.md

@@ -0,0 +1,34 @@
+---
+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.
+
+---

commands/launch-community-activation-series.md

@@ -0,0 +1,36 @@
+---
+name: launch-community-activation-series
+description: Plans and runs a series of community activations (events, AMAs, office hours) with full logistics + follow-up.
+usage: /community-building:launch-community-activation-series --series "Build AI" --format hybrid --cadence monthly --sessions 4 --channels forum,event,live-stream
+---
+
+# Command: launch-community-activation-series
+
+## Inputs
+- **series** – name/theme of the activation series.
+- **format** – virtual | in-person | hybrid.
+- **cadence** – weekly | biweekly | monthly | quarterly.
+- **sessions** – number of activations to plan (default 3).
+- **channels** – comma-separated surfaces (forum, event, live-stream, office-hours, partner-community).
+- **budget** – optional budget or sponsorship notes.
+
+## Workflow
+1. **Programming Design** – define topics, speakers, value props, and desired member actions per session.
+2. **Logistics & Tooling** – create project plan with timelines, owners, templates, and platform configurations.
+3. **Promotion & Enablement** – draft invites, social posts, nurture flows, and champion outreach.
+4. **Run-of-Show Execution** – produce checklists for rehearsal, live moderation, and contingency handling.
+5. **Post-Event Loop** – capture highlights, publish content recaps, update champions, and log feedback.
+
+## Outputs
+- Activation series project plan with milestones, budgets, and staffing.
+- Asset pack: run-of-show, speaker brief, promotion kit, moderation scripts.
+- Post-activation report with attendance metrics, engagement trends, and follow-up actions.
+
+## Agent/Skill Invocations
+- `community-operations-lead` – owns logistics, moderation, and follow-ups.
+- `community-ecosystem-strategist` – ensures programming aligns to objectives.
+- `community-program-matrix` skill – structures calendar + resource allocation.
+- `moderation-safety-playbook` skill – enforces trust & safety workflows.
+- `champion-engagement-system` skill – coordinates VIP/champion participation.
+
+---

commands/run-member-insight-sprint.md

@@ -0,0 +1,34 @@
+---
+name: run-member-insight-sprint
+description: Executes a rapid member insight sprint across forums, interviews, and surveys with routing plan.
+usage: /community-building:run-member-insight-sprint --theme onboarding --sample champions,builders --window 21d --audience product,marketing
+---
+
+# Command: run-member-insight-sprint
+
+## Inputs
+- **theme** – focus topic (onboarding, ai-use-cases, integrations, advocacy, support).
+- **sample** – member cohorts to include (champions, builders, execs, partners, lurkers).
+- **window** – sprint duration (7d, 14d, 21d, custom).
+- **audience** – comma-separated stakeholders for readout (product, marketing, cs, exec, community).
+- **evidence** – optional list of threads, tickets, or recordings to ingest.
+
+## Workflow
+1. **Sprint Setup** – define questions, sampling plan, and instrumentation across channels.
+2. **Signal Collection** – launch prompts, AMAs, micro-surveys, and 1:1 interviews.
+3. **Tagging & Analysis** – apply taxonomy for personas, drivers, sentiment, urgency.
+4. **Narrative & Actions** – craft insight summary, quotes, data, and recommended actions per audience.
+5. **Follow-up & Routing** – create action register, assign owners, and message members on outcomes.
+
+## Outputs
+- Insight sprint report (deck/memo) with top findings, quotes, and metrics.
+- Tagged dataset + member story snippets for reuse.
+- Action tracker linking insights to owners, deadlines, and follow-up comms.
+
+## Agent/Skill Invocations
+- `member-insights-advocate` – leads data capture, tagging, and storytelling.
+- `community-ecosystem-strategist` – aligns insights to strategic priorities.
+- `community-insight-taxonomy` skill – enforces tagging standards.
+- `closed-loop-community-playbook` skill – manages routing + member follow-up.
+
+---

plugin.lock.json

@@ -0,0 +1,89 @@
+{
+  "$schema": "internal://schemas/plugin.lock.v1.json",
+  "pluginId": "gh:gtmagents/gtm-agents:plugins/community-building",
+  "normalized": {
+    "repo": null,
+    "ref": "refs/tags/v20251128.0",
+    "commit": "7f1f5cdd82c64cd58e16821ea78801a99b69887f",
+    "treeHash": "c41c65029eda4acfe439fd38b0c65fee448551fe07d5b50705f0b26c088201a2",
+    "generatedAt": "2025-11-28T10:17:18.616537Z",
+    "toolVersion": "publish_plugins.py@0.2.0"
+  },
+  "origin": {
+    "remote": "git@github.com:zhongweili/42plugin-data.git",
+    "branch": "master",
+    "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
+    "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
+  },
+  "manifest": {
+    "name": "community-building",
+    "description": "Community ecosystem strategy, programming, insights, and governance",
+    "version": "1.0.0"
+  },
+  "content": {
+    "files": [
+      {
+        "path": "README.md",
+        "sha256": "09a9ab6d015b850c9e77c3cacbf0cb5619b8c29344715014fd1e80b46e4e6722"
+      },
+      {
+        "path": "agents/community-ecosystem-strategist.md",
+        "sha256": "2aae3fc0ca2020d1eef2aebbe57cebc73a87c593b2eead1b7443a3e57e2c9d33"
+      },
+      {
+        "path": "agents/community-operations-lead.md",
+        "sha256": "d9c224b5c3ba97219702c4082b5c3159b1ab86747b70ddd7828f6cb7ed44531a"
+      },
+      {
+        "path": "agents/member-insights-advocate.md",
+        "sha256": "661a16b33b970ba4aac64e39998209c54a20559bf5e490a3c27544a979101e14"
+      },
+      {
+        "path": ".claude-plugin/plugin.json",
+        "sha256": "d2a88b8570d99f83a49d93cc381351754753d81e0c44d1d2e7f64e57f8652d03"
+      },
+      {
+        "path": "commands/run-member-insight-sprint.md",
+        "sha256": "0c3b4f2ae283d58fc33a47360396ed5fcdef71968de6ee6980d1c460fae723bf"
+      },
+      {
+        "path": "commands/design-community-strategy.md",
+        "sha256": "9729548e1d6dfb59b44882d5167b3584ec07da8a0c1313a97033e1c13d622a2c"
+      },
+      {
+        "path": "commands/launch-community-activation-series.md",
+        "sha256": "a4ee519545c69b7e3b78aa970cbd89a0cfbe2de474609e6e68195ef98535d27a"
+      },
+      {
+        "path": "skills/closed-loop-community-playbook/SKILL.md",
+        "sha256": "a0b293b7c2d243682321fe55e82ee45a5870aeaaa686b78b7d5579dea2bca740"
+      },
+      {
+        "path": "skills/community-program-matrix/SKILL.md",
+        "sha256": "b61ba4416e614f032286ebf6ee74611385bd34e5c9b2ad7fa5d92e070c94265c"
+      },
+      {
+        "path": "skills/community-insight-taxonomy/SKILL.md",
+        "sha256": "dcfcbb24fd3f093b05d4066891fa43735bc54e6b1d340e65b9345f41e1cd6bbe"
+      },
+      {
+        "path": "skills/moderation-safety-playbook/SKILL.md",
+        "sha256": "1822e9f91cc20fd72bb1ee2cfd06f1a36f95aad27ebae4219a57c47449db72c7"
+      },
+      {
+        "path": "skills/champion-engagement-system/SKILL.md",
+        "sha256": "3695b550dc362608cb0381b9040292bc845a41fd519d1eda23917f1893930f3d"
+      },
+      {
+        "path": "skills/community-kpi-dashboard/SKILL.md",
+        "sha256": "c7607a5e789006db80567189cbaa31288bf71d51ee6a9a155aa5864726415cc0"
+      }
+    ],
+    "dirSha256": "c41c65029eda4acfe439fd38b0c65fee448551fe07d5b50705f0b26c088201a2"
+  },
+  "security": {
+    "scannedAt": null,
+    "scannerVersion": null,
+    "flags": []
+  }
+}

skills/champion-engagement-system/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: champion-engagement-system
+description: Framework for recruiting, activating, and rewarding community champions.
+---
+
+# Champion Engagement System Skill
+
+## When to Use
+- Building community advocacy programs (advisory circles, ambassador tracks, beta councils).
+- Coordinating champion contributions to events, content, referrals, or product input.
+- Monitoring engagement health and risk signals among top advocates.
+
+## Framework
+1. **Selection Criteria** – health scores, expertise, influence, diversity goals, legal clearance.
+2. **Journey Mapping** – onboarding, activation milestones, recognition, renewal.
+3. **Contribution Menu** – speaking, content creation, mentoring, betas, peer support.
+4. **Incentives & Recognition** – swag, access, revenue share, spotlight campaigns.
+5. **Measurement** – track contributions, influenced pipeline, retention, satisfaction.
+
+## Templates
+- **Champion Tiering**: See `references/champion_tiering.md` for levels and benefits.
+- **Champion roster sheet** with scoring, status, and owner.
+- **Program brief** (objectives, commitments, benefits, timeline).
+- Recognition calendar + communication kit.
+
+## Tips
+- Offer multiple contribution tiers to accommodate bandwidth.
+- Create private channels for champions to bond + give feedback.
+- Pair with `launch-community-activation-series` to slot champions seamlessly.
+
+---

skills/closed-loop-community-playbook/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: closed-loop-community-playbook
+description: Processes for routing community insights/actions and communicating outcomes
+  back to members.
+---
+
+# Closed-Loop Community Playbook Skill
+
+## When to Use
+- After capturing member insights or escalations that require action.
+- Coordinating follow-up between community, product, CS, and marketing teams.
+- Demonstrating accountability to members via updates and celebrations.
+
+## Framework
+1. **Intake & Qualification** – log insight ID, theme, severity, evidence, member metadata.
+2. **Routing** – assign accountable owner, squad, and due date with SLA tiers.
+3. **Action Plan** – outline fix/enhancement, dependencies, success metrics, and comms plan.
+4. **Member Comms** – draft acknowledgement, progress updates, and completion announcements.
+5. **Retrospective** – record outcomes, lessons, and new opportunities.
+
+## Templates
+- Insight/action tracker with columns for owners, stage, and communication status.
+- Member update email/DM templates for acknowledgment, progress, completion.
+- Quarterly accountability report summarizing closed-loop wins.
+
+## Tips
+- Tag insights by member cohorts to personalize updates.
+- Celebrate shipped improvements publicly to reinforce participation value.
+- Pair with `run-member-insight-sprint` so every campaign produces accountable actions.
+
+---

skills/community-insight-taxonomy/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: community-insight-taxonomy
+description: Tagging schema for classifying community signals by persona, journey,
+  and business impact.
+---
+
+# Community Insight Taxonomy Skill
+
+## When to Use
+- Standardizing feedback tagging across forums, events, surveys, and interviews.
+- Sharing structured insights with product, marketing, or CS teams.
+- Powering dashboards and AI routing for community signals.
+
+## Framework
+1. **Persona Dimension** – builders, admins, execs, partners, champions, newcomers.
+2. **Journey Stage** – onboarding, activation, adoption, expansion, advocacy, lapse.
+3. **Driver Dimension** – product, support, education, pricing, community experience, roadmap.
+4. **Sentiment & Urgency** – positive/neutral/negative + severity/impact.
+5. **Business Linkage** – map to ARR tier, account health, opportunity pipeline, or churn risk.
+
+## Templates
+- Tag dictionary with definitions, examples, and confidence guidelines.
+- Airtable/Sheet schema with validation + automation hooks.
+- Quick-reference cheatsheet for moderators/interviewers.
+
+## Tips
+- Run monthly taxonomy reviews to merge duplicates and add emerging themes.
+- Capture "what good looks like" examples to maintain consistency.
+- Pair with `run-member-insight-sprint` for auto-tagged datasets.
+
+---

skills/community-kpi-dashboard/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: community-kpi-dashboard
+description: Measurement system tracking engagement, health, and business impact of
+  community programs.
+---
+
+# Community KPI Dashboard Skill
+
+## When to Use
+- Establishing community OKRs or executive scorecards.
+- Reporting on quarterly community performance.
+- Tying community metrics to pipeline, retention, or product adoption.
+
+## Framework
+1. **Health Metrics** – member growth, activation rate, return visitors, content contributions.
+2. **Engagement Metrics** – participation per program, thread depth, event attendance, response SLAs.
+3. **Advocacy Metrics** – champions created, referrals, case studies, beta participation.
+4. **Business Impact** – influenced pipeline, expansion rate, churn reduction, product usage deltas.
+5. **Trust & Safety** – moderation actions, escalation time, sentiment shifts, NPS.
+
+## Templates
+- BI dashboard schema with recommended charts + filters.
+- KPI definition sheet detailing owners, data sources, refresh cadence.
+- Executive digest template translating stats into decisions/asks.
+
+## Tips
+- Blend qualitative highlights with quantitative charts for context.
+- Instrument campaigns/programs with UTM or CRM links to show attribution.
+- Pair with `design-community-strategy` to keep KPIs aligned to objectives.
+
+---

skills/community-program-matrix/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: community-program-matrix
+description: Planning framework for mapping community programming across personas,
+  channels, and cadences.
+---
+
+# Community Program Matrix Skill
+
+## When to Use
+- Building quarterly/annual community programming plans.
+- Balancing content formats across personas, segments, and lifecycle stages.
+- Aligning stakeholders on resource allocation and measurement.
+
+## Framework
+1. **Persona vs. Lifecycle Grid** – map each persona to their stage (new, engaged, champion) and needs.
+2. **Channel Mix** – forums, live events, office hours, partner co-hosts, UGC, social extensions.
+3. **Cadence & Ownership** – define frequency, hosts, moderators, and backup owners.
+4. **Value Proposition** – articulate member value + business value for every cell.
+5. **Measurement Hooks** – KPIs, instrumentation, and health thresholds per program.
+
+## Templates
+- Spreadsheet/Notion template for program grids with filters by persona or channel.
+- Slide + one-pager to socialize upcoming programming.
+- Resource planning worksheet capturing staffing, budget, and tooling needs.
+
+## Tips
+- Highlight "hero moments" each quarter to focus energy and storytelling.
+- Rotate community champions into programming slots to showcase voices.
+- Pair with `design-community-strategy` and `launch-community-activation-series` for auto-generated calendars.
+
+---

skills/moderation-safety-playbook/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: moderation-safety-playbook
+description: Guidelines and workflows for community moderation, trust & safety, and
+  escalation.
+---
+
+# Moderation & Safety Playbook Skill
+
+## When to Use
+- Launching or scaling moderated forums, chats, or live events.
+- Training moderators, ambassadors, or vendors on policies.
+- Handling escalations, abuse reports, or crisis communications.
+
+## Framework
+1. **Policy Matrix** – code of conduct, content types, enforcement tiers, regional considerations.
+2. **Workflow** – intake → triage → resolution → follow-up, with SLAs and ownership.
+3. **Tooling** – moderation dashboards, keyword lists, automation rules, reporting forms.
+4. **Escalation Ladder** – when to engage legal, security, PR, or executive sponsors.
+5. **Post-Incident Review** – retrospectives, comms templates, improvements.
+
+## Templates
+- Moderator guide with sample responses, tone guidance, and decision trees.
+- Incident log + scoreboard for tracking volume, severity, MTTR.
+- Crisis comms outline for public/partner updates.
+
+## Tips
+- Publish a transparent policy summary so members know expectations.
+- Rotate moderators to reduce burnout; provide mental health resources.
+- Pair with `launch-community-activation-series` for real-time event safety coverage.
+
+---