# Capture decisions in Slack

> For the complete documentation index, see [llms.txt](https://falconer.com/docs/llms.txt).

Important decisions happen in Slack, then vanish. Use @Falcon remember to save any fact, decision, or context the moment it happens, right from Slack.


Important decisions happen in Slack, then vanish. The team agrees on a design approach, someone shares a workaround, and a week later no one can find any of it.

Use `@Falcon remember` to save any fact, decision, or context *the moment it happens*, right from Slack. Falcon stores this information as searchable memory, ready to surface when answering questions or writing docs.

![](/docs/images/capture-decisions-remember.png)

## Ask Falcon to remember things

### Choose who can use it

Tell Falcon whether a memory is **private**, for a **team**, or for the **company**. Team scope can include a team or specific colleagues. If your request does not make the audience clear, Falcon asks before saving anything. Only people in that audience can find the memory in later answers.

### Remember a team workflow

Use Remember for repeatable instructions too. For example, tell Falcon: `Remember this as a skill for the support team: when a customer reports an outage, check the incident channel, summarize customer impact, and draft a status update for review.` Falcon saves a skill document for the team, rather than treating the procedure as a single fact. A matching skill can run automatically when a teammate asks for that kind of work. You can edit the skill later, change when it activates, or invoke it from the **/** menu. [Create skill docs](https://falconer.com/docs/use-cases/skill-docs/create-skill-docs.md) explains how to structure the instructions, and [Use skill docs](https://falconer.com/docs/use-cases/skill-docs/use-skill-docs.md) explains how to invoke them.

In any Slack channel, thread, or DM, type `@Falcon remember` to save any fact worth keeping. It can read through long threads instantly to find what you want to save. Use it to remember things like workarounds, architecture decisions, and meeting outcomes.

Falcon confirms creating the memory in a thread. If a conflicting memory already exists, Falcon asks whether you want to replace it before storing the new fact -- keeping you in control of what gets remembered.

**Examples:**

![](/docs/images/capture-decisions-example-1.png)

![](/docs/images/capture-decisions-example-2.png)

## What Falcon does with memories

Once a memory is saved, Falcon treats it as a high-trust source, the same way it treats your documents and code.

When someone asks a related question in Slack, Falcon surfaces the memory with full provenance: who captured it, when, and where.

![](/docs/images/capture-decisions-surfacing.png)

## Next steps

Try it: Type `@Falcon remember [a recent team decision]` in any channel.