proof-writerlisted

# Proof Write: Rigorous Theorem / Lemma Drafting > 🔬 **Model Recommendation**: Run this skill on **Claude Opus** for best results. > Writing rigorous mathematical proofs requires deep reasoning. If your session is > not on Opus, run `/model opus` before invoking. Write a mathematically honest proof package, not a polished fake proof. ## Constants - DEFAULT_PROOF_DOC = `PROOF_PACKAGE.md` in project root - STATUS = `PROVABLE AS STATED | PROVABLE AFTER WEAKENING / EXTRA ASSUMPTION | NOT CURRENTLY JUSTIFIED` ## Context: $ARGUMENTS ## Goal Produce exactly one of: 1. a complete proof of the original claim 2. a corrected claim plus a proof of the corrected claim 3. a blockage report explaining why the claim is not currently justified ## Inputs Extract and normalize: - exact theorem / lemma / proposition / corollary statement - explicit assumptions - notation and definitions - any user-provided proof sketch, partial proof, or intended strategy - nearby lemmas or claims in local notes, appendix files, or theorem drafts if the request points to them - desired output style if specified: concise, appendix-ready, or full-detail If notation or assumptions are ambiguous, state the exact interpretation you are using before proving anything. ## Workflow ### Step 1: Gather Proof Context Determine the target proof file with this priority: 1. a file path explicitly specified by the user 2. a proof draft already referenced in local notes or theorem files 3. `PROOF_PACKAGE.md` in proj