peer_debate
Compare two implementation plans to resolve a software decision, providing full steps, tradeoffs, risks, and verification for each to enable peer review.
Instructions
Before calling: read relevant source files and attach full contents via files. Pass complete diffs/logs — never prose summaries. Set task with goals, affected behavior, and specific concerns. Independently compare Plan A vs Plan B without cross-contamination.
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>",
"plan_a": "<plan_a>",
"plan_b": "<plan_b>",
"repo_path": "<repo_path>",
"idempotency_key": "<idempotency_key>"
},
"name": "peer_debate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | What decision this debate must resolve and what success looks like. | |
| plan_a | Yes | Full Plan A: steps, tradeoffs, risks, and verification approach. | |
| plan_b | Yes | Full Plan B: steps, tradeoffs, risks, and verification approach. | |
| repo_path | Yes | Absolute path to the repository root the peer should work in (e.g. /home/user/my-app). | |
| risk_level | No | Use high for auth, payments, migrations, concurrency, and public API changes. | |
| idempotency_key | Yes | Stable key for this operation (e.g. review-auth-jwt-1). Reuse the same key when retrying after timeout. |