> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidlogs/drive-team/debrief-from-slack.md).

# Debrief from Slack

The team's Slack bot, **@RAID**, files the drive team's notes on the match they're about.

## Post a debrief

In the drive team's channel, mention the bot with the match and what happened:

> @RAID Q22 pulled left in auto, intake jammed twice

The bot replies in the thread with the match it filed to and a link. Replies in that thread add to the same match.

**Which match:** the one you name (`Q22`, `qual 22`, `P3`, `practice`, `playoff 4`, `M11`), else the thread's match, else the newest match at the event. A note posted before the pit logs the match lands on it once they do.

The notes show on the match's [report card](https://docs.raidrobotics.org/raidlogs/pit-crew-guide/report-card.md) and feed the check list.

## Ask the scouts

A mention with an asking word (`ask`, `scout`, `find out`, `check with`, or a `?`) and a team number goes to RAIDScout instead, which answers in the thread:

> @RAID what drivetrain does 254 run?

## If the bot can't find you

You need a RAIDLogs account with a role. The bot matches your Slack email to your login. If they differ, an admin links your Slack ID in **Manage › Users**. The author or an admin can delete a note on the match page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/raidlogs/drive-team/debrief-from-slack.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
