proof-repairlisted

# Proof-Repair — Literature-Backed Repair Plans for Mathematical Proofs > 🔬 **Model Recommendation**: Run this skill on **Claude Opus** for best results. > Repair design + literature verification requires deep reasoning. If your session is > not on Opus, run `/model opus` before invoking. Heavy reasoning (literature search, > verification, full proof writing) will use Opus sub-agents. Takes a `/proofcheck` audit (or a raw .tex file with known issues) and produces self-consistent repair plans with new literature references for every fixable issue. **Pipeline position**: ``` /proofcheck → [THIS SKILL] → /proof-writer Find issues Fix + literature Write complete proofs ``` **Upstream**: `/proofcheck` (produces audit/ with provability triage + blockage reports) **This skill**: audit/ → REPAIR_PLAN.md + patched .bib + per-unit repair files **Downstream**: `/proof-writer` (writes complete corrected proofs for each repair) ## Context: $ARGUMENTS --- ## Step 0: Locate Inputs Parse `$ARGUMENTS` to find the paper workspace. ``` Expected structure (created by /proofcheck): papers/<paper-name>/ paper.tex CHECK_PLAN.md EXECUTION_ORDER.md audit/ 01_index/theorem_inventory.md 02_ledgers/{notation,assumption,constants}_ledger.md 03_dependencies/dependency_graph.md 04_local_checks/section_*/*_check.md 05_adversarial/{hidden_assumptions,counterexamples}.md 06_reports/{issue_log.md, FINAL_REPORT.md} ``` Read these files in order: 1. `audit/06_re