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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when one reviewer angle is insufficient or the user suspects a direction is tunnel-visioned or inherited its framing. Modes: artifact, direction. Not for source or remote-system changes.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
| Field | Bound contract |
|---|---|
| Trigger | One reviewer angle is insufficient, the user asks to "prism this" or review from different angles, one read may be an artifact of how the question was framed, or the user suspects the current direction of work is tunnel-visioned or inherited its framing. |
| Authority | Read-only. No writes; nothing to roll back. No remote mutation. |
| Side effect | A divergence-first report in chat only; create or change no files; bounded fresh zero-context sub-reads are spawned only as inputs to classification. |
| Done | Bait is stripped from the target; every read carries exactly one classification label (artifact mode: divergent-incompatible, divergent-compatible, convergent; direction mode adds ambiguous); shared-root clustering is complete; cluster order follows the mode, with direction mode listing ambiguous clusters first; convergence is labeled reassurance with no consensus wording; one decisive resolving question is stated. |
pass, fail, or unclear) and the single most load-bearing reason supported by the target or supplied context. Do not average or flatten conflicting verdicts. Done when: every lens has one verdict and one load-bearing reason.divergent-incompatible (challenges a premise the direction depends on, or identifies a framing flaw, hidden assumption, or outcome that contradicts the intent), divergent-compatible (adds, reframes, or proposes a meaningfully different path or emphasis without discarding the direction), convergent (independently arrives at the same framing or verdict), or ambiguous (cannot be classified with confidence; include a one-sentence explanation). Do not force-fit a label. Done when: every perspective carries exactly one classification label.none (no lens conflict). Done when: the decisive question is stated, or none (no lens conflict) with the shared verdict.blocked, naming the artifact or access needed; do not substitute a guessed target.blocked: independent lenses unavailable, report the single read with its classification, and explain why a multi-lens verdict would be false precision; do not pad with variations of the same viewpoint.unclear for the affected lens or ambiguous for the affected read and name the missing evidence; do not convert uncertainty into a firm label.All failures preserve the read-only boundary: there is no mutation to roll back.
Return a chat report with sections in this order: Stripped target, Lenses, Verdicts, Divergences, Convergence, Decisive question, Status.
| Section | Content |
|---|---|
| Stripped target | The bare review question (artifact mode) or the stripped direction statement (direction mode). |
| Lenses | Each selected lens or viewpoint and the failure mode it targets. |
| Verdicts | Per lens: the normalized verdict (pass / fail / unclear), the load-bearing reason, and the classification (divergent-incompatible / divergent-compatible / convergent / ambiguous). |
| Divergences | Roots with their divergent perspectives clustered underneath. Artifact mode: incompatible divergence first, then compatible. Direction mode: ambiguous clusters first, then incompatible, then compatible, then convergent. |
| Convergence | Convergent perspectives described as reassurance, never proof; direction mode notes the framing was inherited, not chosen. |
| Decisive question | The single question whose answer would resolve the deepest disagreement, or none (no lens conflict) with the shared verdict. |
| Status | complete when all lenses evaluated and all perspectives classified; partial when some reads were obtained but not all; blocked when the target is missing, independent lenses are unavailable, or artifact-mode framing cannot be stripped. |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。