consult_peer
Get peer review on technical proposals and architectural decisions. Receive a structured verdict (AGREE, SUGGEST_CHANGES, or DISAGREE) to guide consensus.
Instructions
Antigravity-backed peer consultation for architectural/technical consensus. For Codex orchestration, prefer delegate_task_readonly with resource_group: "review". Use during PLANNING phase to validate proposals before implementation. Supports iterative rounds: send proposal, get feedback, revise, resend until AGREE. The peer responds with a structured verdict: AGREE, SUGGEST_CHANGES, or DISAGREE.
Returns a task_id immediately (non-blocking). Use get_task_result to check the verdict. The peer runs without a timeout — it will work until done. Progress is visible via get_task_result.
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": {
"context": "<context>",
"proposal": "<proposal>"
},
"name": "consult_peer"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Working directory for file access. Defaults to current working directory. | |
| model | No | Model to use. Default: Auto. | |
| context | Yes | Project context: what are we working on, constraints, requirements. | |
| proposal | Yes | Your technical proposal or architectural decision to review. | |
| previous_rounds | No | Summary of previous discussion rounds (if iterating toward consensus). |