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 independent proposals on a contested decision need cross-critique before choosing, reusing the original authors. Not for parallel multi-stance investigation: use council.
$ npx -y skills add OutlineDriven/odin-claude-plugin --skill cross-critique --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cross-critiqueContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: cross-critique 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.'
| 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. |
1. 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. 2. 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. 3. 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. 4. 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. 5. 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. 6. Synthesize directly by weighing evidence quality, not vote count. Lead with the recommendation, then:
Done when: the synthesis states the recommendation, convergence, strongest cons, survival rationale, and remaining disagreement with confidence and unknowns. 7. 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.
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.