proof-writer

# Proof Write: Rigorous Theorem / Lemma Drafting > 🔬 Run this skill on **Claude Opus**. Writing rigorous proofs needs deep reasoning; > run `/model opus` first if your session is not on Opus. Write a mathematically honest proof package, not a polished fake proof. **The unit of completion is the closed obligation, not prose.** A proof is finished when every nontrivial obligation it raises is discharged into a typed closure object, not when it reads smoothly. This single idea drives the whole skill: it is what stops the model from quitting early (an open obligation is visible and costly) and from faking (you cannot prose your way into a typed closure). ## Constants - DEFAULT_PROOF_DOC = `PROOF_PACKAGE.md` in project root - STATUS = `PROVABLE AS STATED | PROVABLE AFTER WEAKENING / EXTRA ASSUMPTION | NOT CURRENTLY JUSTIFIED` - VERIFICATION = `Verified | Conditionally verified | Gap found` (defined in `../stat-shared-references/proof-closure-machinery.md`, single source of truth) - SCRIPT = `../stat-shared-references/scripts/proof_gap_scan.py` - ASSUMPTION_LOCK = `assumptions.lock.md` — the framework's shared assumption store (schema + discipline in `../stat-shared-references/assumptions-lock-protocol.md`). Theorems invoke assumptions by ID from here; they do not declare their own. ## Context: $ARGUMENTS ## Goal Produce exactly one of three terminal outputs: 1. a complete proof of the original claim, every obligation closed; 2. a corrected (usually weaker) claim plus a co...