vibedoc_spec_context

Gather what the project already says about one capability so you can draft its spec: matching epics (or the ones you pass) with their done tasks' Goal and Acceptance criteria, related docs, knowledge entries and the existing spec. Read-only, capped at ~6k tokens (oldest tasks cut first). Draft the spec from it and propose it with vibedoc_propose_edit at docs/specs/<capability>.md; never write it directly.

Parameters

Name	Type	Required	Description
capability	string	yes	Spec slug, e.g. "board-views"
epics	string[]	no	Epic ids to use instead of keyword matching, e.g. ["R010", "R022"]
query	string	no	Words to match epics, docs and entries by (default: the slug's words)

Call it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "vibedoc_spec_context",
    "arguments": {
      "capability": "<string>"
    }
  }
}