record_decision
Record a coding decision before implementing changes so reviewers can approve or reject it, keeping architecture, API, and security choices visible and auditable.
Instructions
Record a decision before making the changes that carry it out, so reviewers can approve or reject it. Use one call per decision (architecture, data model, API, business rule, dependency, security, performance, testing, quality).
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": {
"title": "<title>",
"kind": "<kind>",
"why": "<why>",
"files": "<files>"
},
"name": "record_decision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| why | Yes | the reason in one or two plain sentences | |
| kind | Yes | architecture, data-model, api, business-rule, dependency, security, performance, testing, quality or other | |
| risk | No | what could go wrong, if anything | |
| files | Yes | files this decision changes | |
| title | Yes | short headline, at most 8 words, e.g. Rate limit per client IP | |
| alternatives | No | options considered and not chosen |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| status | Yes |