How to Write Slack Channel Purpose, Topic, and Canvas from a Team Brief
Slack channels rot when the topic invents a 15-minute ack SLA and a PagerDuty app you did not install. This is not Discord and not a caption engine. Purpose, topic, and a canvas outline are enough.
The matching generator is the Slack Channel Purpose, Topic, and Canvas from a Team Brief prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Honor the naming prefix and public vs private
Write Slack channel names, purposes, topics, and canvas outlines from a team brief. No invented members, bots, or SLAs. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
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]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Count topic characters out loud
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: workspace, channel intents, people, apps, SLAs. Forbidden: members not in People, bots not in Apps, SLAs not in SLA.
- Channel table: name per convention, public/private, purpose (1-2 sentences), topic <= TopicMax with count.
- Canvas outline per channel that Canvas lists: headings only from Brief. No fake screenshots.
- Pin suggestions: only if Brief names a doc. Do not invent a Google Drive URL.
- App mentions: only Apps. If NONE, do not recommend Slackbot workflows as if they were installed.
- Out of Slack: quote Out (HR cases, PHI, etc.).
- People: handles only from People. If NONE, write no named owners.
- Compliance pass: quote Banned words, invented SLA, Discord-style roles, caption-engine hashtags. Cut them.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Mention only apps that are installed
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- 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.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Keep PHI and legal holds out of the channel copy
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (slack channel purpose topic, slack canvas outline, team brief to slack) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.