scan-decisions

Extract and classify project decisions from Loopbench records into an evidence-backed report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of which decisions were made, which still need human judgment, and which are just automatic follow-ups. This Skill audits an existing Loopbench project and produces an evidence-backed decision report before asking anyone to decide anything. ## Core Features & Use Cases - Deterministic decision scan: Runs loopbench decisions scan to collect accepted contracts, recorded human gates, and process gates as facts, with optional bounded local Codex/Claude session reading via --with-sessions. - Lead classification: Classifies Git surface signals and needs-analysis items into current_human, automatic_followup, or past_inferred using explicit observable criteria, with mandatory evidence references and tradeoff options. - Validated report rendering: Writes analysis.json, validates it against the scan (rejecting bad references, duplicates, or transcript leakage), and renders report.html separating explicit past decisions from inferred ones. - Use Case: A maintainer returning to a long-running project asks "what decisions did this project make and what still needs my judgment?" The Skill scans the repository, separates direction-setting choices from automatic follow-ups, and returns an HTML report with cited evidence. ## Quick Start Ask the assistant to scan this Loopbench project for past decisions and open questions that still need human judgment.

Frequently Asked Questions about scan-decisions

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

FAQPage Schema
How do I audit past decisions in a Loopbench project?

Run `loopbench decisions scan` from the project root, then read the generated scan.json and report.html in .loopbench/decision-scan. Accepted contracts and recorded human gates appear as past_explicit facts, while Git signals appear only as analysis leads.

How to separate human decisions from automatic follow-ups?

Classify an item as current_human when multiple viable choices optimize different goals or reversal is costly. Classify it as automatic_followup when an accepted goal fixes the outcome and a test, linter, or build can verify correctness.

When should I use scan-decisions versus challenge-decision?

Use scan-decisions to inventory and classify decisions across a whole project before any choice is made. Use challenge-decision only after a concrete high-impact decision boundary has already been selected from the scan results.

Does the decision scan include AI chat sessions?

Only when the user explicitly requests it via the --with-sessions flag, which reads a bounded set of local Codex and Claude sessions. Raw session content is printed to the host, never saved, and must not be copied into repository files.

Why does the scan reject my analysis.json file?

Validation rejects missing files, invalid line ranges, unknown event or commit references, duplicate identifiers, raw transcript text, and human choices lacking alternatives. Every item must cite at least one accepted evidence reference such as a full Git hash or project-relative file range.

Can scan-decisions analyze multiple projects at once?

No, the command scans exactly one Loopbench project root per run and is not designed for cross-project batch analytics. Run it separately in each project repository you want to audit.