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

# Documents and versions

> How planspace documents evolve, get reviewed, and become durable design intent.

Every planspace has a document. The document is the team-readable artifact that turns agent conversation into a proposal, design, implementation plan, or reviewable spec.

Documents are useful because they let non-technical teammates participate without reading an entire agent transcript. They can read the current version, comment on exact passages, and approve a direction before engineers delegate execution.

## What belongs in the document

Good Scott documents usually include:

* the problem and desired outcome
* constraints, risks, and open questions
* architecture or product decisions
* prototype notes and screenshots when relevant
* implementation plan and rollout notes
* links to the code, PRs, or follow-up planspaces that matter

## Versions

Scott saves document versions as the plan changes. A version is the stable thing a teammate can review and approve.

Use versions when:

* comments have changed the direction and you need a clean review point
* a reviewer needs to approve a specific plan, not a live draft
* a PR should link to the exact design version it implements
* you want to compare original intent with actual execution later

## Editing

The author can keep iterating with Scott in chat, edit the document directly, or incorporate selected comments back into the conversation. The goal is not to preserve a perfect first draft. The goal is to make team feedback explicit and keep the document aligned with what the team intends to build.

## Review handoff

When the document is ready for sign-off:

1. Save or open the version you want reviewed
2. Use **Share** and choose **Review**
3. Select reviewers and explain what they should focus on
4. Reviewers approve or reject from the review panel

Once approved, that version becomes the strongest reference when your agent [pulls context from Scott](/developer-tools/pull) and when the [Scott GitHub App](/developer-tools/scott-ci) reviews a PR.

## PR feedback

When a pull request links back to a planspace, Scott can connect implementation work to the document that shaped it. This is how the document set keeps updating: original design intent, review feedback, implementation decisions, and shipped code stay connected.