Contract

Input: a mathematical statement to prove (or a set of statements to evaluate).
Output: a Markdown proof artifact saved to the repo, with statement, strategy, steps, verification, and theorem citations.
Scope: generates reasoning only; no code execution, no file system writes beyond the Markdown artifact.
Rule: generates reasoning only; no code execution, no file system writes beyond the Markdown artifact.
Rule: documented standards override defaults; explicit project rules take precedence.
Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.

Provenance

Question	Answer
What is the source of truth?	The user's request, originating spec/issue, and the skill's declared outputs
What is in scope?	Work covered by the skill's acceptance criteria and completion rules
What is explicitly out of scope?	Files, behaviors, and decisions outside the skill's declared boundary
Who or what consumes this artifact afterward?	The next skill in the workflow or the user
What evidence proves it is done?	Completion criteria met, artifact saved, validation passed
What risk remains?	Subjective judgment calls, missing context, or external dependency failures