vibe_checkpoint
Gate code writing behind user-approved checkpoints: ask the user's approach first, confirm design tradeoffs, and require explicit approval of exact code changes before implementation.
Instructions
VibeWise: open a checkpoint BEFORE doing the work. kind=build: ask how the USER would approach the problem (their reasoning first, never your design). kind=design: present the agreed design + tradeoffs for confirmation. kind=implement: present the exact code changes for approval - the only gate that authorizes writing code.
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": {
"kind": "<kind>",
"name": "<name>"
},
"name": "vibe_checkpoint"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | ||
| name | Yes | Short checkpoint title, e.g. 'Folder membership'. | |
| proposal | No | design/implement: the proposal or exact code scope. | |
| projectPath | No | ||
| consequences | No | Why it matters; consequences the user accepts. | |
| proposedAdditions | No | Agent-suggested details, clearly separated from user decisions. |