> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryscott.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team pulse

> How teams use Scott to see design intent, review health, and execution drift.

Team pulse is the operating view Scott is building toward: a way to see what is being planned, what has been approved, and how implementation compares to original design intent.

## Why it matters

Agent output makes execution faster, but it also makes misalignment easier to miss. Teams need to know:

* which proposals are waiting on feedback
* which plans have been approved
* which pull requests are linked to approved intent
* where implementation diverged from what the team reviewed
* which areas of the product lack current design context

## Inputs

Scott's team-level view comes from the same daily workflow:

1. [Sync](/developer-tools/sync) keeps recent agent work discoverable
2. [Push](/developer-tools/push) turns useful agent threads into planspaces
3. [comments](/collaboration/comments) and [reviews](/collaboration/reviews) capture team feedback
4. [Scott GitHub App](/developer-tools/github-app) links pull requests to planspace intent
5. landed code feeds execution context back into the document set

## Signals

Useful team signals include:

| Signal            | What it answers                                         |
| ----------------- | ------------------------------------------------------- |
| Review queue      | Which plans are waiting on decision makers?             |
| Approval coverage | Which shipped work had reviewed design intent?          |
| PR links          | Which pull requests implemented a given planspace?      |
| Design drift      | Where did implementation differ from the approved plan? |
| Stale plans       | Which documents need to be updated after code landed?   |

## Document OS

The goal is a continuously updating document OS for teams: not static specs, not disconnected PR comments, and not lost agent chats. Scott keeps the original design intent, team review, implementation record, and future execution context in one place.