agent-environment-retr…
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.
$ npx -y skills add OutlineDriven/odin-claude-plugin --skill cross-lens-converge --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cross-lens-convergeContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.
name: cross-lens-converge description: 'Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.' disable-model-invocation: true
| Field | Bound contract | |---|---| | Trigger | One reviewer isn't enough because the failure modes are heterogeneous, or a claim looks strong to its author and needs cross-lens pressure before it ships | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | None (read-only analysis); returns a convergence picture and the single resolving question | | Done | The result reads as a picture not a checklist: a reader sees which lenses agreed, which disagreed, and the one question that matters, and can act on it without re-running the analysis |
The claim or artifact under pressure must be supplied. Candidate failure modes may be supplied or derived from the artifact. When supplied, they are trusted input and must not be re-derived.
1. Receive the artifact and the candidate failure modes. If the failure modes are not supplied, enumerate them from the artifact. Done when: the artifact is received and failure modes are supplied or enumerated. 2. Collapse candidates that describe the same failure mode into one lens. Assign exactly one lens to each genuinely distinct failure mode that remains. Done when: each distinct failure mode has exactly one lens, with duplicates collapsed. 3. Give each lens exactly one load-bearing reason it would reject or weaken the claim. A lens with no load-bearing reason is dropped before running, not coerced into agreement. Done when: every retained lens has one load-bearing reason; reasonless lenses are dropped. 4. Run every lens independently against the artifact. Record, per lens, its verdict as one of agrees, disagrees, or cannot-decide, and the single reason that drives that verdict. Done when: every retained lens has a verdict and its driving reason recorded. 5. Do not average, merge, or majority-count the verdicts. Disagreement is the product; preserve which lenses agreed and which disagreed. Done when: verdicts are preserved per-lens without averaging or majority-counting. 6. From the disagreed and cannot-decide lenses, identify the one question whose answer would resolve the most lens disagreements. If no single question resolves more than one, name the question that resolves the highest-stakes disagreement. If no lens disagrees and at least one lens cannot-decide, name the one question whose answer would let the undecided lenses reach a verdict. If every lens agrees, the resolving question is none. Done when: the single resolving question is identified, or none is set when every lens agrees. 7. Return the convergence picture: per-lens verdict and load-bearing reason, the agreed set, the disagreed set, and the single resolving question. Done when: the convergence picture is returned with per-lens verdicts, agreed set, disagreed set, and resolving question.
A convergence picture: each lens's verdict and its one load-bearing reason, the agreed set, the disagreed set, and the single resolving question. Read-only; no state transition.
Formerly the ODIN Claude Plugin. The repository URL is unchanged. Outline-Driven Development, nicknamed ODIN, is a highly opinionated code-agent skill library: principles-first engineering, surgical editing, and workflow automation, published as installable
Repo: OutlineDriven/odin-claude-plugin
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
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,…
Use when a human explicitly asks for a full repository agent-compatibility pass returning a scored report with prioritized fixes. Not for tasks that require…
Use when setting up a project, auditing agent command permissions, or asking which read-only bash commands and domains to allow. Not for remote, credential,…
Use when asked to build or review a CLI intended for coding agents and return flag-driven, pipeline-safe, idempotent design advice. Not for running or…
Use when the user asks to make the skills framework work in a new harness, IDE, or CLI. Not for remote, credential, publish, deploy, or irreversible changes.