> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-work-on-documents-from-slack.md). # How to work on documents from Slack A doc gets shared in a channel, someone has a question about it, and then the thread and the doc drift apart. The comment lives in Slack, the context lives in the doc, and nobody's sure which one is current. **The short answer** Bring a doc into the thread and work it from there `@Rhythms comment on the doc: this needs a launch date` Comment, reply, resolve, or ask Rhythms to read it for you. Nothing changes in the doc until you say so. *** ## Before you start * [**Set up Rhythms in Slack**](/getting-started/getting-started-in-slack/getting-started-with-rhythms-in-slack.md) * **Access to the doc.** Rhythms can only work with documents it has access to — the same sharing and permissions that apply in the product apply here. It can't see docs that haven't been shared with it. *** ## Step 1: Bring the doc into the thread ## If it's already shared in the channel Reference it the way you'd point a teammate to it. **Try it:** `@Rhythms summarize the doc above and pull out the open questions` > **Also works:** "what's the state of the doc Dana posted?" · "give me the short version of this one" · "what's still unanswered in here?" ## If you want Rhythms to find it Ask, and it looks across your Library. **Try it:** `@Rhythms find the working doc for the partner directory` > **Also works:** "pull up the partner directory doc" · "which doc has the launch plan in it?" **Tip:** **Name the doc you mean when a channel has several in play.** "The doc above" is enough in a quiet thread, but in a busy one it's the difference between Rhythms working the right document and asking you which one. **Long docs are fine.** Rhythms reads the whole thing, and it can point you at a specific section rather than summarizing all of it if you ask for that instead. ## If you have comment notifications enabled on Slack Reply to the notification with your updates. Rhythms updates the comment without you having to leave Slack. ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-8195cc56c466e611dc81ee2f0dbff415941964b6%2F1787600957120-image.png?alt=media) *** ## Step 2: Comment, reply, and resolve without leaving the thread Once the doc is in the conversation, work it the way you'd work a comment thread. **Try it:** `@Rhythms comment on the doc: this needs a launch date before we can scope it` Reply to an existing comment, or resolve one once it's settled. **Try it:** `@Rhythms reply to Dana's comment: confirmed, shipping after the test` > **Also works:** "resolve the comment about the launch date" · "resolve Dana's comment" · "who has open comments on this doc?" ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-befe989ae37d6ab68596da6b1f9204e9f7f000ba%2F1787601370252-image.png?alt=media) **Every comment posts to the doc itself**, so anyone opening it later sees the same conversation you had in Slack. Comments, replies, and resolutions all sync. Nothing is Slack-only — which is the whole point. ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-491b81972efd72981875e07fdb26f4d8b41eb7d4%2F1787601409367-image.png?alt=media) *** ## Step 3: Optional · Ask questions, or hand off the next step Once Rhythms has read the doc, keep going in the same thread. **Try it:** `@Rhythms what did we decide about the launch date?` > **Also works:** "who raised the concern about scope?" · "what did we say about pricing in here?" Useful when a doc has sat untouched for a while and you need the state of it before a meeting, without opening it yourself. **Try it:** `@Rhythms what's changed in this doc since last week?` When the answer is more work rather than an answer, hand that over in the same breath. **Try it:** `@Rhythms turn the open questions into a follow-up doc and share it with Sam` > **Also works:** "draft a summary I can post in #leadership" · "share this with the pricing group" Sharing from Slack grants access the same way sharing from the product would — it's the same permission change, not a copy. *** ## If something didn't work Rhythms says it can't find the doc It hasn't been shared with Rhythms, or you're describing it differently than it's titled. Try the exact name, or share it and ask again. It worked on the wrong doc A busy channel with several docs in play. Name the doc explicitly rather than saying "the doc above." My comment isn't showing in the document Check it actually saved rather than sitting as an unconfirmed draft in the thread. Someone can't open the doc I shared from Slack Sharing follows product permissions. If they couldn't open it there, the Slack share doesn't change that — grant them access explicitly. *** ## Try Next * [**Check in on your goals from Slack →**](/getting-started/getting-started-in-slack/how-to-check-in-on-your-goals-from-slack.md) * [**Manage goals from Slack →**](/getting-started/getting-started-in-slack/how-to-manage-goals-from-slack.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-work-on-documents-from-slack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.