challenge-decision

Reviews Loopbench contracts, human gates, and commit-sized work units with adversarial decision memos.

1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/hideh1231/loopbench --skill challenge-decision-hideh1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenge-decision
Source: https://github.com/hideh1231/loopbench/tree/main/skills/challenge-decision
Command: npx skills add https://github.com/hideh1231/loopbench --skill challenge-decision-hideh1231

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent-completed work and proposed contracts can be accepted on weak evidence, hidden assumptions, or unchallenged reasoning. This Skill provides an independent, read-only adversarial review that challenges decisions before they are accepted, without making the decision itself. ## Core Features & Use Cases - Decision-boundary review: Challenge a proposed contract before acceptance or a pending human gate after process evidence exists, using loopbench challenge packet and loopbench challenge record. - Commit-sized checkpoints: Review coherent, non-trivial work units before they become a commit, storing bounded memos under work-unit-reviews with source-backed task notes. - Reviewer independence ordering: Prefer a different model family in a fresh/read-only context, fall back to same-family fresh context with explicit labeling, and always ask the user before sending material to an uncleared external service. - Structured rubric and simplicity assessment: Grade declared rubric criteria with traceable evidence and map new long-lived mechanisms to contract goals. - Use Case: Before accepting a contract that changes project scope, run a contract-target challenge review to surface unsupported claims, omitted options, and the strongest counter-hypothesis, then record a verdict of clear, concerns, blocker, or unknown. ## Quick Start Ask the assistant to run a challenge review on the pending human gate for the current Loopbench task and record the verdict memo.

Frequently Asked Questions about challenge-decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a proposed Loopbench contract before accepting it?

Run loopbench challenge packet with the task id and the contract target to build a bounded review input, inspect the evidence in a fresh read-only context, then record the verdict with loopbench challenge record and a Markdown memo.

How do I review a commit-sized work unit that has no pending human gate?

Build a bounded input from the accepted contract, plan, unit diff, and focused check receipts, then store the memo under .loopbench/tasks/<task-id>/work-unit-reviews/ and register a source-backed task note with loopbench note.

When should I use a different model family as the reviewer?

Prefer a different model family in a fresh read-only context for consequential decisions, since same-family review gives fresh context but less viewpoint diversity. Ask the user first if the review sends material to a service not already cleared for it.

When can I skip the commit-sized review checkpoint?

Skip only when the unit has no meaningful semantic or decision change, such as formatting only, regenerated output from unchanged reviewed source, typo fixes, or obvious one-line mechanical fixes with a direct check. The builder must disclose the exact skip reason.

Does a passing challenge review replace external verification?

No. Reviewer agreement, even from another model family, is not external scientific evidence. Tests, measurements, primary sources, and domain experts remain separate oracles, and the reviewer never makes the final human decision.