Coordinate GitHub, Notion and Slack from one conversation

Read first, then propose the change

A useful cross-service workflow starts by reading the relevant repository, page or conversation, then summarizes the exact proposed update before writing anywhere.

1. 1Read the named repository, Notion page or Slack channel.
2. 2Identify the requested state and any missing detail.
3. 3Present the proposed write and target.
4. 4Execute only after the applicable permission check.

Writes need explicit intent

GitHub changes, Notion edits and Slack messages are consequential operations. Naming a service is not enough to authorize a write; the request must say what should change, and Ask operations create an approval ticket.

Slack membership still matters

A Slack bot can only read or post where its installation and channel membership allow it. A permission from Slack does not automatically make the bot a member of every channel.