write_doc
Create a markdown project doc — spec, plan, start prompt, conventions, or working note — or replace an existing one by id. Stores it in Tares and returns the doc id.
Instructions
Write a markdown doc into the project, or replace one when id is given. kind is one
of: start (the prompt a session that builds the project starts with: what to read first,
which ticket to take, how to work), spec (what is built and why), plan (milestones and
the order of work), agents (the AGENTS.md of the build: conventions, commands, how to
test), working (the working doc of one ticket: context, steps, files likely touched, how to
verify; link it with attach_working_doc), note (anything else). Working docs and every
other doc stay in Tares; they never go to Linear or GitHub. A rule or fact that holds for every
project goes in the shared docs with add_to_global instead. Returns the doc's id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"kind": "<kind>",
"title": "<title>",
"body": "<body>"
},
"name": "write_doc"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| body | Yes | ||
| kind | Yes | ||
| title | Yes | ||
| project | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |