📱 Social Media
Slack Channel Purpose, Topic, and Canvas from a Team Brief
Write Slack channel names, purposes, topics, and canvas outlines from a team brief. No invented members, bots, or SLAs.
0Reviews
Prompt
Act as a Slack admin writing channel purpose, topic, and canvas copy from a team brief. You write Slack channel naming, purpose (the short description), topic, and a Canvas outline from a team brief. You do not invent members, bots, or SLAs. This is not a Discord announcement kit and not a LinkedIn or TikTok caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace name and naming convention: [Workspace] - Team brief (mission, rituals, tools): [Brief] - Channels I want (intent, public or private): [Channels] - People and handles I may mention: [People or NONE] - Bots and apps actually installed: [Apps or NONE] - SLAs I may print: [SLA or NONE] - Words I must not use: [Banned] - Canvas sections I allow: [Canvas] - Topic character comfort (Slack topic is short): [TopicMax or 120] - What must stay out of Slack: [Out] Generate: 1. Honesty ledger: workspace, channel intents, people, apps, SLAs. Forbidden: members not in People, bots not in Apps, SLAs not in SLA. 2. Channel table: name per convention, public/private, purpose (1-2 sentences), topic <= TopicMax with count. 3. Canvas outline per channel that Canvas lists: headings only from Brief. No fake screenshots. 4. Pin suggestions: only if Brief names a doc. Do not invent a Google Drive URL. 5. App mentions: only Apps. If NONE, do not recommend Slackbot workflows as if they were installed. 6. Out of Slack: quote Out (HR cases, PHI, etc.). 7. People: handles only from People. If NONE, write no named owners. 8. Compliance pass: quote Banned words, invented SLA, Discord-style roles, caption-engine hashtags. Cut them. Constraints: - Slack channel copy and canvas outline. Not Discord, not Teams, not social captions. - Never invent members, bots, or SLAs. - Print topic character counts. - Private vs public only as Channels state. - No emojis unless Brief already uses them.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Workspace: Harbor Ledger, prefix team- Brief: SE plus CS sit together for iOS rec bugs. Ritual: 15 min standup in writing at 16:00 UTC. Tools: Jira PAY, App Store Connect. No PHI. Channels: 1 public team-ios-rec for the work; 1 private team-ios-rec-escalations for customer-named bugs People: priya (SE), omar (CS). No intern handle. Apps: Jira Cloud app installed. No PagerDuty app. SLA: NONE (do not invent 15-minute ack) Banned: Discord, growth hashtag, 24/7, guaranteed response Canvas: for the public channel only: mission, standup template, links (Jira PAY, no URLs beyond that name), out-of-band rules TopicMax: 120 Out: legal holds, payroll data, customer SSNs
Example Output
1. Ledger. Workspace Harbor Ledger, prefix team-. Channels: public team-ios-rec; private team-ios-rec-escalations. People priya omar. App: Jira Cloud. SLA NONE. Ritual 15 min written standup 16:00 UTC. Tools Jira PAY, App Store Connect. Out: legal holds, payroll, SSNs. Forbidden: intern, PagerDuty, 15-min ack, Discord, 24/7. 2. Public team-ios-rec. Purpose: Day-to-day iOS rec work for SE and CS. Topic (72): Written standup 16:00 UTC. Jira PAY. Owners priya and omar. No PHI. Private team-ios-rec-escalations. Purpose: Customer-named iOS rec bugs. Topic (58): Private. Customer names stay here. Still no SSN. 3. Canvas (public only). Mission; standup template at 16:00 UTC; links: Jira PAY (URL NOT IN INPUTS); out-of-band: legal holds, payroll, SSNs not here. No canvas for the private channel requested. 4. Pins. None unless a doc URL appears (none). 5. Apps. Jira Cloud only. No PagerDuty. 6. Out. Legal holds, payroll data, customer SSNs. 7. People. priya and omar only. 8. Compliance. Cut: Discord, growth hashtag, 24/7, guaranteed response. Gaps: canvas for private channel, Drive URL, intern, SLA. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.