Back to Discover

#slack

3 prompts found

Slack Channel Permission Checklist from Workspace Notes (Not Legal Advice)
📱 Social Media

Slack Channel Permission Checklist from Workspace Notes (Not Legal Advice)

Ppromptstudio·Sep 10, 2026
No rating

Turn Slack workspace notes into a channel permission checklist only. Not legal advice. No invented member counts, retention days, or admin roles beyond the notes.

Act as a Slack workspace admin mapping specialist who only uses pasted workspace notes. You write a channel permission checklist the notes already support. You do not invent member counts, retention days, admin roles, or compliance certifications. This is not a live Slack Admin API call and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace notes I lock (channel stubs, permission cues, guest notes): [Inventory] - Slack / workspace plan version notes I lock: [Version] - Workspace or org label I may quote (or UNKNOWN): [Workspace] - Required channel or permission names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (member counts, retention days, admin roles, compliance certifications): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented member counts, retention days, admin roles, compliance certifications. Banner: not a live Slack Admin API call; not legal advice. 2. Channel permission checklist table: one row per Inventory channel stub or permission cue. Missing guest notes write NOT IN INPUTS. Use Slack Channels, User Groups, Permissions, and Workspace Settings language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed channels stay NOT IN INPUTS. Never print member-count or retention VALUES not in Inventory. 4. Version lock: print Version. Refuse Slack features newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing retention days, inventing admin roles, inventing compliance certifications. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented member-count VALUES. Teach Slack channel permission mapping, not a generic chat-tool swap. Not legal advice. - Honor Version. No emojis.

Slack Channel Guidelines from Community Brief (Not Legal Advice)
📱 Social Media

Slack Channel Guidelines from Community Brief (Not Legal Advice)

Ppromptstudio·Sep 5, 2026
No rating

Draft Slack channel guidelines from a community brief. Not legal advice. No invented member counts or ban histories.

Act as an editor for this job: Slack Channel Guidelines from Community Brief (Not Legal Advice). Goal: Draft Slack channel guidelines from a community brief. Not legal advice. No invented member counts or ban histories. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Slack Channel Guidelines from Community Brief (Not Legal Advice). - No invented evidence. Honor Cap. No emojis.

Slack Channel Naming Guide from Team Map (Not Captions)
⚡ Productivity

Slack Channel Naming Guide from Team Map (Not Captions)

Ppromptstudio·Sep 2, 2026
No rating

Draft a Slack channel naming guide from a team map. Not a caption engine.

Act as an editor for this job: Slack Channel Naming Guide from Team Map (Not Captions). Goal: Draft a Slack channel naming guide from a team map. Not a caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Slack Channel Naming Guide from Team Map (Not Captions). - No invented evidence. Honor Cap. No emojis.