← ClaudeAtlas

evidence-selflooplisted

Evidence self-loop for surveys: read evidence bindings + evidence packs, then write an actionable upstream TODO plan (which stage/skill to fix) before writing more prose. **Trigger**: evidence self-loop, evidence loop, evidence gaps, binding gaps, blocking_missing, 证据自循环, 证据缺口回路.
WILLOSCAR/research-units-pipeline-skills · ★ 511 · Code & Development · score 81
Install: claude install-skill WILLOSCAR/research-units-pipeline-skills
# Evidence Self-loop (C3/C4 fix → rebind → redraft) Purpose: make the evidence-first pipeline converge **without writing filler prose**. This skill reads the *intermediate evidence artifacts* (briefs/bindings/packs) and produces an actionable TODO list that answers: - Which subsections are under-supported? - Is the problem mapping/coverage (C2) or evidence extraction (C3) or binding/planning (C4)? - Which skill(s) should be rerun, in what order, to unblock high-quality writing? ## Inputs - `outline/subsection_briefs.jsonl` - `outline/evidence_bindings.jsonl` (expects `binding_gaps` / `binding_rationale` if available) - `outline/evidence_drafts.jsonl` (expects `blocking_missing`, comparisons, eval protocol, limitations) - Optional (improves routing): - `outline/evidence_binding_report.md` - `outline/anchor_sheet.jsonl` - `papers/paper_notes.jsonl` - `papers/fulltext_index.jsonl` - `queries.md` ## Outputs - `output/EVIDENCE_SELFLOOP_TODO.md` (report-class; always written) ## Self-loop contract (what “fixing evidence” means) - Prefer fixing **upstream evidence**, not writing around gaps. - If an evidence pack has `blocking_missing`, treat it as a STOP signal: strengthen notes/fulltext/mapping, then regenerate packs. - If bindings show `binding_gaps`, treat it as a ROUTING signal: either enrich the evidence bank for the mapped papers, expand mapping coverage, or adjust `required_evidence_fields` if unrealistic. Recommended rerun chain (minimal): - If C3 evide