my_work
Retrieve a person’s ready, in-progress, bouncing, and review-returned tickets, led-project milestones, desk items, and spec questions by crew or project so an orchestrator starts only their work.
Instructions
What belongs to the person whose key this is, across the projects handed to a crew that
they can see: ready (their tickets that can start: nothing they wait on is open), in_progress
(their tickets a station holds, with the holder and stage), bouncing (those of them that
came back from review three or more times: count, ladder 3 or 5 and the last reason),
led_projects (projects they
lead, with the milestones whose tickets are all delivered: milestones_ready_to_check),
desk (the open desk items addressed to them) and spec_questions (the open questions a
spec asked them as the owner of a repo, always empty without an enterprise licence: answer each
with answer_question). crew
names your crew; empty means the crew this session belongs to. The orchestrator of a crew works from this, so it starts
only its own person's tickets. project (a name or an id) keeps spec_questions to that
project: question numbers restart in each project, so name it when you work on one. Empty
lists the questions of every project; a name or id you cannot see is an error 404 ("no
project 'x' you can see"), so name it exactly. Needs a key with a person.
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": "my_work"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| crew | No | ||
| project | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |