Use when designing, reviewing, or documenting community-operations automation, including recurring data collection, report assembly, activity reminders, draft generation, status-board updates, skill/version checks, AI/bot/operator handoffs, execution states,…
Use when turning daily community operations into a concise daily report, daily log, work recap, owner update, standup note, or personal community-ops record. Separates completed public actions, drafts, analysis, follow-ups, risks, data gaps, and tomorrow…
Use when writing, rewriting, reviewing, or polishing community-operations language, including announcements, activity posts, reminders, result posts, daily/weekly reports, public articles, skill descriptions, resume bullets, interview stories, stakeholder…
Use when diagnosing, designing, coordinating, operationalizing, or reviewing an end-to-end community operations system; when a request spans onboarding, activities, creators, paid members, reports, automation, support risk, operator writing, SOPs, or…
Use when producing community weekly reviews, weekly reports, metric summaries, decision notes, retrospective plans, or next-week operating priorities. Connects activity data, onboarding, creator signals, paid/member care, support risks, content assets, and…
Use when designing, reviewing, or packaging community activities, campaigns, challenges, contests, AMAs, events, reminders, submissions, voting, rewards, result announcements, or activity retrospectives for any community platform. Produces operator-ready…
Use when identifying, nurturing, or operating community creators, contributors, superusers, ambassadors, featured members, user-generated content, showcases, tutorials, case studies, attribution, permissions, or turning submissions into reusable…
Use when designing, auditing, or improving community newcomer journeys, onboarding questions, welcome flows, first-action prompts, start-here pages, role/access routing, activation checklists, or early retention paths across Discord, forums, Slack,…