Write Document Tool
write_documentCreate a project document or save a new Markdown version after approval; pass the read base version to prevent overwriting a teammate’s concurrent save and request a merge.
Instructions
Creates a project document or saves a new version of one: Markdown, the whole text. Only when the person asks or agrees, after showing them the text or the changes. To change an existing document, read it first and pass the version you read as base_version: if a colleague saved in the meantime, nothing is overwritten and you are told to merge into the new version. With client_visible: true the project's client sees the document too (read-only, the current version), only when the person asks for that; share_with_client changes it later. Never secrets, passwords or tokens.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The whole document, in Markdown (not only the changed part). | |
| note | No | What changed, in one short line, e.g. "Added the color palette". | |
| repo | No | The git remotes of the working directory (git remote -v). | |
| title | Yes | The document's title, e.g. "Brief", "Logo concept", "Decisions". An existing title saves a new version of that document. | |
| project | No | Project slug or name, if not this session's. | |
| session | No | This session's id, from the cemainou line at the start of the session. The session's project wins over the repo. | |
| base_version | No | The version you read with read_document. Required to change an existing document; leave it out to create one. | |
| client_visible | No | true: the project's client sees the document too; false: only the team. Only when the person asks; only on a project visible to its client. |