Ticket draft plan
ticket_draft_planWrite or revise the ticket's plan document: the markdown remediation/execution plan reviewers critique and humans approve. Include the proposed change, blast radius, rollback strategy, and verification steps. Drafting (or re-drafting after changes were requested) sets the plan state to 'drafted'; follow with ticket_request_review to invite the peer reviewer.
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": {
"plan": "<plan>"
},
"name": "ticket_draft_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | Yes | The full plan document (markdown). Replaces the previous revision; the old text stays in the timeline. | |
| ticket_id | No | The ticket UUID. Optional when ticket_number is given. | |
| plan_actions | No | Optional: the action classes this plan will use, as [{"tool": "restart_deployment", "namespace": "payments"}]. Declare every step that changes something. A desk whose organisation has opted those action classes into unattended execution, and whose assignee runs at autonomy 'auto', can then start executing without a human click; a plan that declares nothing, or that names one step outside the trusted set, waits at the human approval gate exactly as before. | |
| ticket_number | No | The per-organisation ticket number. |