Tool reference · Tasks, workflows & decisions
phase_transition
Closes the current phase of a task and opens the next one, optionally attaching artifacts and notes.
local stdio server writes
Caution. Phases only move forward and cannot be skipped. Valid names are van, plan, creative, build, reflect and archive, limited to those allowed for the task level.
When to use
- Planning is done and you are ready to start building.
- You want to attach outputs (a plan file, a PR link) to the phase you are entering.
- The work is finished and the task should move to reflect or archive.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
task_idrequired | string | — | — |
new_phaserequired | string | — | — |
artifacts | object | — | — |
notes | string | — | — |
Example
Arguments
{
"task_id": "BILL-142",
"new_phase": "plan",
"artifacts": {
"plan": "docs/rate-limit-plan.md"
},
"notes": "Token bucket per API key"
}Result shape
{
"task_id": "BILL-142",
"from_phase": "van",
"to_phase": "plan",
"entered_at": "2026-09-25T09:30:11Z",
"rules_preview": "Rules for phase 'plan': call self_rules_context(project=..., phase='plan') to load."
}Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
advance a task to the next phase.