📱 Social Media
Community AMA Prep Kit: Answers, Pinned Post, and Moderation
Prep a Reddit, Discord, or Slack AMA: pinned post, 20 drafted answers, ban-list questions, and a live moderation run-of-show.
0Reviews
Prompt
Act as a community lead prepping a live AMA that will not embarrass the guest or the mods. You write for the actual platform's norms. You protect the guest from gotchas they cannot answer, and you protect the room from a sales pitch. Inputs: - Platform: [Reddit / Discord / Slack / Circle / other] - Community: [Community] - Guest: [Guest] - Topic and off-limits: [Topic] - Date, duration, timezone: [When] - Proof and facts the guest can use: [Proof] - Product or company relationship: [Relationship] - House rules: [Rules] - Audience skill level: [Audience] - Past drama to avoid: [Drama] - Links allowed: [Links] Generate: 1. Positioning: One paragraph the room will believe. Why this guest, why now, what "success" is (useful answers, not upvote count). 2. Pinned post: Paste-ready. Include who, topic, start/end time with timezone, how to ask (thread vs new post), disclosure of Relationship, off-limits, and where answers will live after. Match Platform format (Reddit post vs Discord channel topic vs Slack canvas). 3. Run of show: T-24h, T-1h, start, +15 min, midpoint, last 10 min, T+2h archive. Who types, who mods, who DMs the guest. 4. Seed questions (12): Mix of beginner, advanced, skeptical, and "show your work." Each should be answerable from Proof. Mark 5 to plant in the first 10 minutes if the room is quiet. 5. Draft answers (20): Short, specific, in the guest's likely voice. Each answer: 80-160 words, one example from Proof, one "I don't know / depends" if needed. Number them. Include 3 answers that politely refuse Off-limits. 6. Moderation card: What to lock, what to remove, what to leave (rude-but-on-topic vs ad vs personal attack). 5 canned mod replies. How to handle "this is an ad." How to handle a question that asks for legal, medical, or insider info not in Proof. 7. Aftercare: Recap post outline, 5 pull quotes from the drafted answers, a "we will not" list (no stealth follow-up sales). Honor Drama: do not reopen it. Constraints: - Do not invent bios, metrics, or past posts. - Do not write fake user names as if they already asked. - If Proof is too thin for 20 real answers, write fewer and list the facts you still need. - No "excited to sit down." No engagement bait in the pin. - The guest may plug once, in the pin and in one answer, if Relationship is disclosed. Not in every answer. - Honor Off-limits and Rules.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Platform: Discord Community: Ops Commons, a 4,200-member Discord for ops leads at 20-200 person companies Guest: Maya Chen, Director of Ops at Northline (58 people). First AMA. Not a vendor. Topic and off-limits: How they cut 4 tools from an 11-tool stack. Off-limits: Northline's clients by name, salaries, anything about a rumored acquisition, legal advice on contracts with vendors. Date, duration, timezone: Tue Aug 25, 2026, 12:00-1:00pm America/New_York, #ama channel Proof and facts the guest can use: 11 tools down; kept Slack, Notion, Harvest; cut Asana, Otter, a wiki, one extra AI summarizer; 3-week office-hours migration; 10 days of messy Harvest-Notion time entries; email and Drive still exist; they are not a software org so Jira is out of scope; team of ops is Maya + 1 specialist Product or company relationship: none; Maya is a member already House rules: no vendor pitches in AMA; questions in thread under the pin; be civil; mods are Sam and Rae Audience skill level: mixed, lots of first-time ops leads, a few chiefs of staff Past drama to avoid: a vendor did a stealth AMA in March and got roasted; do not look like that Links allowed: none required; personal LinkedIn ok in the pin only
Example Output
1. Positioning Maya is a member, not a vendor. She cut four tools at a 58-person services company and will show the cut rule, the 3-week migration, and the 10 days that were ugly. Success is specific answers, not a sales thread. 2. Pinned post # AMA: Maya Chen (Northline ops) on cutting 4 tools Tue Aug 25, 2026, 12:00-1:00pm America/New_York in #ama. Maya Chen is Director of Ops at Northline (58 people) and a member of this server. This is not a vendor AMA. No product to buy. Topic: 11 tools down. Kept Slack, Notion, Harvest. Cut Asana, Otter, a wiki, and an extra AI summarizer. 3-week office-hours migration. 10 messy days of time entries. How to ask: reply in this thread only. One question per reply. Mods: Sam and Rae. Off-limits: client names, salaries, acquisition rumors, legal advice on vendor contracts. She will say "not answering that." After 1:00pm ET the thread stays for reading. Recap gets pinned. No follow-up DMs selling software. Maya's LinkedIn lives in this pin only. 3. Run of show T-24h: Sam posts the pin. Rae sets slowmode 10s. T-1h: Sam pings @ops-leads once. No @everyone. Start: Maya pastes a 4-line hello + the cut rule. Sam posts 2 seed questions. +15: if quiet, Rae drops 3 more seeds. Vendor pitch: delete + DM the rule. Midpoint: Sam restates off-limits. Maya answers in bursts of 3. Last 10: two remaining questions; no 1:1 stack reviews in DMs. T+2h: recap, unslowmode, pin 7 days. 4. Seed questions (12) Plant first: (1) Cut rule in one sentence? (2) Why did Asana lose? (3) Why keep Slack? (4) What broke for 10 days? (5) Office hours with 2 ops people? More: (6) What were the 11 tools? (7) Why did AI notes die? (8) How did first-time coordinators take it? (9) What would you not copy onto a software team? (10) Email and Drive still exist, right? (11) When is a wiki worth keeping? (12) What is still messy today? 5. Draft answers (20), compressed 1. Cut rule: if two tools store the same source of truth, one dies. 2. The 11 included two AI summarizers, a dead wiki, Harvest, Slack, Notion, Asana, Loom, Drive, email, custom intake. 3. Kept Slack, Notion, Harvest. Email and Drive still exist. I will not say "three-tool company." 4. Asana lost because tasks already lived in Notion databases. 5. Otter + extra summarizer died because people did not read the notes. 6. Wiki died as a second Notion nobody opened. 7. Slack stays: clients live there. 8. Not a software org. I will not map this onto Jira. 9. Migration: 3 weeks of office hours, Maya + 1 specialist. No memo-only rollout. 10. Harvest-Notion time entries were messy for 10 days. Expected, still hated. 11. Office hours: two slots a day, bring the task you cannot find. 12. First-time leads got a checklist, not a town hall. 13. Loom was in the 11 but not a source of truth, so it was not one of the four cuts. 14. Do not copy this where tickets are the product. 15. Still messy: time entries when someone skips Harvest. 16. Refuse client names: patterns only. 17. Refuse salaries: out of scope. 18. Refuse acquisition rumors: not answering. 19. Plug once: not selling a course. LinkedIn is in the pin. 20. No free stack audits in DMs; ask here so others get the answer. 6. Moderation card Lock: off-limits repeats after one refuse. Remove: vendor links, hire-me, personal attacks. Leave: blunt "this fails at 200 people" if it stays on the work. Canned: (1) Vendor pitches are out. (2) One question per reply. (3) She is not answering client names. (4) Legal/vendor-contract questions are off-limits. (5) This is not the March vendor AMA. Guest is a member. Insider/legal: "Not in the facts she can use. Moving on." 7. Aftercare Recap: cut rule, four tools named, 3-week hours, 10-day mess, Slack-for-clients, Jira out of scope. Pull: "one source of truth," "nobody read the summaries," "office hours not a memo," "clients live in Slack," "not answering that." We will not: DM a "resource," reopen the March vendor fight, post a discount code.