cp-skill-revise-autoreason

## EXECUTE NOW **Target: $ARGUMENTS** (exactly one note path or filename - if empty, ask which note) **Experimental.** This is the conservative note-revision adaptation of AutoReason, based on `related-systems/autoreason/`. Use it when you want to test the tournament workflow. This skill defaults to prose-preserving revision, but it may produce a separate substantive-revision sidecar when the revisions reveal that claim, evidence, source, or argument changes are actually needed. Keep that sidecar out of the B/AB blind tournament and never auto-apply it. Each pass compares three versions: - **A**: the unchanged incumbent for this pass. - **B**: a revision motivated by a critic's identified problems. - **AB**: a synthesis of A and B. Three fresh judge agents rank blind candidate packets. Aggregate with Borda count. "Do nothing" is a first-class option: if A wins twice consecutively, stop. ## Step 0: Resolve The File Resolve `$ARGUMENTS` to a full path. If it is a bare filename, search `kb/notes/` for a match. Read the file in full to confirm it exists and capture the original content. Before running the loop, report the call budget: up to 5 passes. A normal pass uses 7 fresh Codex sub-agents (critic, revision author, synthesizer, post-candidate auditor, 3 judges). Early stops may use fewer, bounded reruns may use more, and the substantive-revision sidecar uses one additional sub-agent when triggered. ## Step 1: Initialize Use a workshop directory so the original note...