Plan a Lampa feature change
plan_changeGenerate a step-by-step implementation plan for a Lampa change, including inferred targets and coupling risks, so you can scope edits to existing code before drafting patches.
Instructions
Generate a step-by-step implementation plan with inferred targets, a reverse-ref sample, and coupling risks for a Lampa change. Call this before draft_patch; unlike draft_patch it does not invent diffs, unlike trace_symbol it covers a whole request rather than one file/event, unlike scaffold_plugin it plans edits to existing code. request='add a sleep timer' + scope_hint='player' concatenates into feature inference; empty inference still returns a plan (not an error). Snapshot-only — does not execute or write; heuristic — not a guarantee; affected-surface list caps at ~12 files.
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": {
"request": "<request>"
},
"name": "plan_change"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Plain-language description of the change, e.g. 'add a sleep timer to the player'. | |
| scope_hint | No | Optional hint for which feature area is involved, e.g. 'player' or 'plugins/iptv'. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| markdown | Yes | Human-readable markdown report. Always present, including empty-result cases. Does not write files. |