Community Programs

---
name: community-programs
description: Design, launch, operate, grow, audit, or retire member-to-member programs: customer, practitioner, contributor, support, advocacy, forum, chat, and subreddit communities, including platform choice, norms, moderation, programming, roles, health metrics, and phase gates. Use for community-led growth and community operations; use organic-social for broadcast channels and creator-partnerships for paid or partnered voices.
license: MIT
metadata:
  version: "2.0.0"
  author: MTEnt
---

# Community Programs

A community needs recurring member-to-member value. An audience, mailing list, or promotional channel is not automatically a community.

If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [community-system.md](references/community-system.md) for models, platform choice, phases, programming, governance, health metrics, and output.

## Operating contract

1. Define who needs to interact, the recurring value, host role, desired member behavior, business relationship, and operating capacity.
2. Choose ownership and platform from actual communication, identity, privacy, moderation, search, and integration needs.
3. Design onboarding, norms, safety, programming, contribution recognition, staff roles, escalation, and exit.
4. Measure useful participation, solved problems, retained contributors, customer outcomes, and cost.
5. Require approval before inviting people, changing access, sending announcements, or using member content.

Do not seed fake members, simulate conversations, harvest private discussion, or turn support obligations into unpaid community labor.

## Return

Community thesis, member jobs, model and platform rationale, founding cohort, onboarding, norms, programming, roles, moderation and escalation, health dashboard, phase gates, budget, and retirement conditions.