vibedoc_propose_plan
Propose a plan for the user to review: kind "breakdown" (tasks: pass epic for an existing epic, newEpic to create the epic with the tasks, or neither for loose tasks with no epic) or kind "roadmap" (new horizons and epics: horizons + epics; an epic's parent is an existing horizon id or a horizon key in this plan; epic body = one outcome sentence, a blank line, then **In scope:** / **Out of scope:** / **Done when:**). Does NOT write anything: the user sees the plan in the UI, can uncheck items, and accepts. Validated against the current files; on errors, fix the plan and call again. Each task body is the full markdown below the meta block (## Goal, ## Context, ## Scope, ## Files, ## Acceptance criteria, ## Verify). dependsOn lists keys of earlier tasks in this plan or existing task ids ("T030"). covers lists the epic's scenario ids (## Scenarios → ### S1: …) the task makes true.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
plan | object | yes |
Call it
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "vibedoc_propose_plan",
"arguments": {
"plan": "<object>"
}
}
}