Plan a code change
plan_changeCall ONCE at the start of a coding task. A complete brief: files and line ranges to change, the key functions in full with their callers, the existing pattern to follow, decisions not to break and the only tests to run. From the code graph, not guesses.
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": {
"task": "<task>",
"repository": "<repository>"
},
"name": "plan_change"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | What you are about to do, in plain words (e.g. "add rate limiting to the refresh token endpoint"). | |
| paths | No | Files or folders you already know are involved. | |
| terms | No | Words this codebase would use for the task, e.g. ["throttle"] for "rate limiting", ["revoke", "grant"] for "disconnect apps". | |
| detail | No | map: a short edit map (files, line ranges, pattern, unit tests); full: also the key functions in full. Default: map for code changes, full for plans and questions. | |
| targets | No | Real names in this repo the task is about (functions, classes, constants, files), from the vocabulary in the server instructions, e.g. ["AuthController.refresh"]. | |
| repository | Yes | Public GitHub repository as "owner/name" (e.g. "pallets/flask") or its github.com URL. |