Create a new channel — AI Prompts for Slack

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

We need a dedicated channel for the Q3 reliability workstream so the project updates don’t clutter…

We need a dedicated channel for the Q3 reliability workstream so the project updates don’t clutter #eng. Create a new channel named #reliability-q3 with a description: Q3 cross-team reliability improvements. Add members: @Ravi, @Marta, @Lina, @Diego, @Priya. Set channel to private and invite the listed members.

Improve — make it easier to accept

Before I create the project channel, make it easy for execs and engineers to find status: the…

Before I create the project channel, make it easy for execs and engineers to find status: the channel name should show quarter and purpose, description should include meeting cadence and key docs, and membership should include stakeholders. Proposed: #reliability-q3 — description: Q3 reliability initiatives. Weekly sync Wed 10am. Relevant doc: Google Drive link. Members: @Ravi (eng lead), @Marta (pm), @Lina (SRE), @Diego (backend), @Priya (finance). Private channel.

Decide — diagnose the stuck moment

I want a channel where engineers and stakeholders can coordinate Q3 reliability work. I’m not sure…

I’m about to create a new channel for the Q3 reliability program but I’m unsure who must be invited.

I want a channel where engineers and stakeholders can coordinate Q3 reliability work. I’m not sure whether to make it public or private, and whether to include Finance and Legal now or add them later. If I include too many people I’ll get noise; if I include too few decisions stall. Who should be in from day one, what name and description make the purpose obvious, and should it be private?

Become — change the pattern

We create a new channel for every initiative and then either nobody uses it or it floods us with…

I keep creating project channels but they either die or become noisy duplicates.

We create a new channel for every initiative and then either nobody uses it or it floods us with noise. I waste time maintaining membership and duplicating info across channels. What habit should I change — naming, onboarding members, or channel lifecycle rules — so project channels stay active, focused, and easy to archive?

Next to this one

Other team chat work people do in Slack.

Change profile photo Configure app notifications Connect an app or integration Create a channel topic or purpose Create a group DM Create a reminder for channel Create a reminder for self Create a shared channel with external team Create an event or meeting note Create custom emoji

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt