lean-model-update
Installation
SKILL.md
lean-model-update
Ground rules
- Standalone. Standalone skill: use the current request or explicit arguments. Read applicable project instructions and only task-relevant context.
- No prerequisites. No Lean installation, CLI, configuration or companion skill is required; do not install a workflow or create workflow files as prerequisites. Existing project rules apply.
- Depth. Use requested procedure depth, or standard by default. High adds relevant boundary cases and stronger evidence; ultra adds cross-part consistency and contradictory evidence where relevant. Depth does not change model reasoning settings.
- Records. Keep decisions in conversation unless a suitable project record exists or the user requests persistence.
Input and result
- Input. Establish the requested endpoint: research/proposal, evaluation, or application of an exact approved mapping.
- READY. A proposal concludes READY with sources, candidate changes, destination, budget and untested assumptions; no evaluation or edit is implied.
- DONE. Evaluation concludes DONE only for the approved trials, reporting actual outcomes and limits. Application concludes DONE only after the approved diff and configuration validation.
- BLOCKED and FAILED. Missing access, budget, required review or exact-change approval is BLOCKED for the affected endpoint; an unresolved executed validation failure is FAILED.
- Recovery. Preserve completed evidence and give the next action rather than restarting the whole workflow.