Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi.
The English summary is being prepared. Showing the original description.
Use when independent proposals on a contested decision need cross-critique before choosing, reusing the original authors. Not for parallel multi-stance investigation: use council.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
| Field | Bound contract |
|---|---|
| Trigger | Multiple independent proposals on a contested decision exist (round-one proposals are on the table). |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. The synthesis is conversational output. |
| Side effect | Read-only second round reusing existing subagents; no repo mutation. |
| Done | Synthesis notes convergence, strongest objections, and surviving option. |
Verify the prerequisite: at least two genuinely divergent proposals exist from an independent first round. If the proposals already strongly agree, or the question has an objective answer verifiable directly, stop. A second round adds latency and tokens without resolving real disagreement. Done when: divergence and independence are confirmed, or the round is stopped with the reason reported.
Assemble each proposal's core recommendation and reasoning (not full transcripts). Label them neutrally (Proposal A, B, C) and anonymize authorship where practical to reduce bandwagon bias toward whichever author sounds most confident. Done when: each proposal is assembled with neutral labels and anonymized authorship.
Reuse the same subagents from round one rather than spawning fresh ones, so each retains its investigation context. Send each author only the other proposals (not its own). Done when: each round-one subagent is reused and receives only the other proposals.
Ask each author to assess every alternative:
Insist on both pros and cons for each alternative. A critique that credits a rival's strengths is more useful than a reflexive defense of the author's own proposal. Done when: each author returns pros, cons, recommendation-change assessment, and ranking for every alternative.
If a critique is thin or unsupported, send a focused follow-up to that same author rather than discarding it. Done when: every thin critique is followed up or marked non-convergent after a second attempt.
Synthesize directly by weighing evidence quality, not vote count. Lead with the recommendation, then:
Keep the critique round read-only; do not mutate the repo, files, or remote state. Done when: no repo, file, or remote mutation occurs.
A conversational synthesis containing: the recommendation; where authors converged or changed their minds after seeing alternatives; the strongest objection raised and whether it is decisive; why the recommended option survives critique against the decision criteria; and remaining risks, unknowns, and confidence. No repo mutation.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi.
The English summary is being prepared. Showing the original description.
Use when configuring ADC sampling time, DMA-driven ADC, calibration, or DAC channel setup on bare-metal MCUs. Not for the DMA stream itself: use dma-baremetal.
The English summary is being prepared. Showing the original description.
Use when creating AF_XDP sockets, configuring UMEM and XSK rings, writing an XDP redirect program, or choosing copy versus zero-copy mode. Not for full kernel bypass: use dpdk.
The English summary is being prepared. Showing the original description.
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
The English summary is being prepared. Showing the original description.
Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.
The English summary is being prepared. Showing the original description.
Use when a repo needs agent setup, AGENTS.md added or made lean, CLAUDE.md audited, or agent instructions scored or pruned. Not for remote, credential, publish, deploy, or irreversible changes.
The English summary is being prepared. Showing the original description.