proof-writer

To write a rigorous mathematical proof, provide the exact theorem statement and explicit assumptions to generate a structured proof package. This outputs a step-by-step, justification-heavy document detailing the exact claim, strategy, and open risks.

Formalizing assumptions and dependencies for a lemma requires creating a structured dependency map within a PROOF_PACKAGE.md file. This process captures exact statements and nearby lemmas to automate rigorous proof development rather than informal sketches.

Yes, you can identify missing steps in formal mathematical proofs through gap analysis. This process locates gaps in your reasoning and proposes corrected claims with corresponding justifications to ensure mathematical clarity.

Extracting exact claims and notation from local drafts uses context extraction to collect assumptions and nearby lemmas. This workflow automation streamlines proof development by assembling precise statements into a structured verifiable format.

Generating a complete proof package requires a PROOF_PACKAGE.md target file format. This structure ensures the output document captures exact claims, explicit assumptions, and a structured dependency map for verifiable formal reasoning.

You should avoid automated proof drafting when you only need informal sketches or lack explicit assumptions and a structured dependency map. The process requires formalization inputs to deliver justification-heavy documents with exact claims and open risks.