hand_over
Hand a specced project to your crew: record every repo it spans, who handed it over and to which crew, so the orchestrator picks it up on its next tick.
Instructions
Hand a specced project to the crew: Tares records it with every repo it spans, who handed
it over and to which crew, and the orchestrator picks it up from Tares on its next tick.
repos is one {path, name} per repo:
path the absolute folder it is checked out in on this machine, name its GitHub repo
(owner/name), the repo that holds the plan first. A later call adds repos, never replaces
them. A folder is kept for your crew only: a teammate's crew building the same project hands
over its own clone's folder with the same name. autonomy only when the person wants this project stricter than the crew
(L3-review: every merge waits for their yes). repo (one path) is the older form. Then
send your own crew's orchestrator (the reply names it) a [TF:SHIP] message with
SendMessage so it starts now rather than on its tick. If your crew is not running (the
reply says so), tell the person to run tares factory crew up first. Other people's crews
pick up their own tickets on their next tick. Needs a key with a person. A project kept for
later (set_later) starts with it.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "hand_over"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | No | ||
| repos | No | ||
| project | No | ||
| autonomy | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |