sop-flow
Run the agentic-sop-kit workflow (extract→compute→report, or a declared topology) and report the DRAFT result. Works…
Get an independent adversarial SECOND OPINION on a finished DRAFT — check its claims against its evidence (no fabrication, no overreach) before a human approves. FULL mode reads an agentic-sop-kit run dir's trace; DEGRADED mode reviews any document with supplied inputs.
> /plugin marketplace add s0912758806p/agentic-sop-to-workHow it fires
How this command gets triggered: by you, by Claude, or both.
/second-opinionContext preview
What this command does when you run it.
Get an independent adversarial SECOND OPINION on a finished DRAFT — check its claims against its evidence (no fabrication, no overreach) before a human approves. FULL mode reads an agentic-sop-kit run dir's trace; DEGRADED mode reviews any document with supplied inputs.
description: Get an independent adversarial SECOND OPINION on a finished DRAFT — check its claims against its evidence (no fabrication, no overreach) before a human approves. FULL mode reads an agentic-sop-kit run dir's trace; DEGRADED mode reviews any document with supplied inputs. argument-hint: "<run_dir> | <doc> --inputs <file...> | (no args = bundled demo)"
You are an **independent, skeptical second reader**. Your job is to attack a finished DRAFT and find where its **claims are not backed by its evidence** — fabricated/transcribed numbers, invented identifiers/dates that should be `【待補】`, wrong PASS/FAIL verdicts, and conclusions the data don't support. You **review the output's honesty**, NOT source-code quality (that is `/code-review`) and NOT the workflow architecture (that is `agentic-workflow-audit`). You **never** approve or reject — a human owns the verdict.
`$ARGUMENTS`
Let `ROOT="${CLAUDE_PLUGIN_ROOT}"` and `OUT="${CLAUDE_PROJECT_DIR:-.}/.second-opinion-runs"`.
Run the deterministic checker. It writes `second_opinion.{json,md}` and an LLM envelope `llm_input.json` into the run's output dir.
Note the output dir it prints (the `wrote …` lines). Call it `RUNOUT`.
Read `RUNOUT/llm_input.json`. It gives you `draft_text`, `declared_sources`, `claims`, `already_settled`, `focus`, and `rules`. Acting as an adversary:
layer could not parse). The deterministic layer already owns `#1/#2/#3` where it could.
in `claim`, and justify it in `evidence` by citing a `declared_sources` token or stating `NO SOURCE`. **Do not** invent input values. **Do not** re-flag anything in `already_settled`.
Write your candidate findings to `RUNOUT/llm_candidates.json`, conforming to `secondop/redteam_schema.json` (an object `{"findings": [...]}`). If you find nothing beyond what the deterministic layer caught, write `{"findings": []}`.
Re-run review with your candidates. The code clamps them to SOFT/advisory, drops any that fail the evidence gate, suppresses re-litigation of settled slots, and enforces the pass cap (`SECONDOP_MAX_LLM_PASSES`, default 1):
Show the final `RUNOUT/second_opinion.md`. Summarize: HARD (deterministic) vs SOFT (advisory) counts, and any accusations the evidence gate dropped (transparency that the red-team was itself checked). Then **STOP** with an explicit, human-owned decision — do not approve, reject, or file anything yourself:
> ✋ **Human decision required.** Second Opinion is advisory and does not decide. > Choose: **[Approve the draft]** · **[Send back for fix]** · **[Override a specific finding (give a reason)]**
Loop Engineering — make an agent's loop produce verifiable progress, stay honest, and stay bounded, by deterministic mechanism rather than vibes.
Run the agentic-sop-kit workflow (extract→compute→report, or a declared topology) and report the DRAFT result. Works…
Lint a record / dataset / kit run for ALCOA+ data integrity (attribution, contemporaneity, completeness, accuracy, consistency).…
Lint a Claude Code plugin / marketplace against house invariants, or scaffold a new grammar-conformant plugin skeleton.