> ## 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.

# Planspaces

> The shared UI where teams turn agent work into documents, feedback, reviews, and execution context.

A planspace is where a team aligns on what should be built before handing work back to agents. It combines a conversation, a living document, connected sources, comments, reviews, approvals, and sharing controls.

Use planspaces for:

* prototype writeups and design proposals
* engineering plans that need PM, design, or leadership feedback
* implementation context that should survive beyond one agent thread
* approved intent that should later be pulled into execution with the Scott plugin

## How planspaces start

You can create a planspace three ways:

1. **From Sync Chat** - pin or write up a useful synced session after [Sync](/developer-tools/sync)
2. **From your coding agent** - ask the Scott plugin to [push](/developer-tools/push) from a focused thread
3. **From the app** - start a new planspace and describe what you want Scott to draft

For daily team workflows, pushing from your coding agent is usually the fastest path. It turns active agent work into a shareable document while the idea is still fresh.

## The planspace layout

The planspace UI is built for shared review:

* **Chat** is where the author works with Scott and folds feedback back into the proposal.
* **Document** is the readable artifact teammates review, edit, comment on, and approve.
* **Sources** show the GitHub repos or uploaded files Scott can use for grounded answers.
* **Comments** anchor feedback to exact document text.
* **Reviews** create an approval record for a specific saved version.
* **Share** controls who can collaborate, review, or receive the planspace.

## Recommended team flow

1. Start with real work: a prototype, implementation sketch, investigation, or product proposal.
2. Ask your coding agent to [push](/developer-tools/push) it into a planspace.
3. Attach code context with the [Scott GitHub App](/planspaces/connected-sources) when architecture matters.
4. Share the planspace with engineers, PMs, designers, or leadership.
5. Use [comments](/collaboration/comments) for targeted feedback and [reviews](/collaboration/reviews) for approval.
6. Ask a fresh agent thread to [pull](/developer-tools/pull) the reviewed context from Scott.
7. Link the PR back to the planspace with the [Scott GitHub App](/developer-tools/scott-ci).

## Roles

| Role      | Send messages | Edit document | Comment | Review | Manage members |
| --------- | :-----------: | :-----------: | :-----: | :----: | :------------: |
| Owner     |      Yes      |      Yes      |   Yes   |   Yes  |       Yes      |
| Editor    |      Yes      |      Yes      |   Yes   |   Yes  |       No       |
| Commenter |       No      |       No      |   Yes   |   Yes  |       No       |
| Viewer    |       No      |       No      |    No   |   No   |       No       |

## What good looks like

A strong planspace is not a polished spec dropped at the end of the process. It is a working design record that captures:

* the rough prototype or proposal that started the thread
* what the team questioned or changed
* the version that was approved
* the context an agent needs to execute
* the PRs that implemented the approved design