skills.rest
nicholls-inc
nicholls-incOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lean-spec

Convert signed-off informal verification specs into type-checked Lean 4 stubs.

5|Updated Mar 4, 2026
Search Tags:#formal verification#lean#proof development#spec translation#verification pipeline
One-click install
npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill lean-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-spec
Source: https://github.com/nicholls-inc/claude-code-marketplace/tree/main/crosscheck/skills/lean-spec
Command: npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill lean-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of translating informal formal-verification specifications into structured Lean 4 files for formal reasoning and verification.

Core Features & Use Cases

  • Automated translation of signed-off informal specs into Lean stub files.
  • Validation that the informal spec has a proper human sign-off and exists at the correct path.
  • Iteration to produce buildable, type-checked Lean code with sorry placeholders, enabling formal verification pipelines.
  • Use Case: Formal verification engineers can rapidly generate initial Lean stubs from signed informal specs to start their proof development or code review.

Quick Start

Invoke the lean-spec skill with the module name; it will process the informal spec at the designated path and produce a Lean stub ready for further development.

Frequently Asked Questions about lean-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Lean 4 specification stubs from informal specs?▼

To generate Lean 4 stubs, invoke the skill with your module name to process the signed-off informal spec at its designated path. It outputs type-checked Lean files with sorry placeholders, ready for formal proof development.

What is the process for translating an informal verification spec into Lean?▼

Translating an informal spec into Lean requires validating human sign-off at the correct path, then converting the text into buildable Lean 4 code. The process iterates until the output is type-checked and includes sorry placeholders for proofs.

Do I need a signed-off informal spec before starting Lean proof development?▼

Yes, a signed-off informal spec at the correct file path is required. The tool validates this human sign-off before converting the informal verification requirements into buildable Lean 4 stub files for formal reasoning.

Are the generated Lean 4 files type-checked and ready for formal verification pipelines?▼

Yes, the generated Lean 4 files are fully type-checked and buildable. They include sorry placeholders for proofs, ensuring the stubs integrate smoothly into formal verification pipelines and mathematical modeling workflows.

What are the limitations of using automated spec translation for Lean 4?▼

The limitation of automated spec translation is that it produces Lean 4 stubs with sorry placeholders rather than completed proofs. Engineers must still manually develop the formal proofs to finish the verification pipeline.

Related Skills

Explore More Software Engineering Skills→
TheMostlyGreatTheMostlyGreat
8

writing-plans

Convert approved specs into execution plans with exact paths and verification gates.

Community
Advanced
fmhallfmhall
1

lean-monad-proofs

Optimize Lean 4 proofs involving monads and do-notation.

Community
Advanced
nicholls-incnicholls-inc
5

lean-impl

Translate Python, Go, or Dafny source code into formal Lean 4 models.

Official
Advanced
0bserver070bserver07
3

formalize-informal-proof

Convert informal mathematical proofs into Lean 4 code for formal verification.

Community
Advanced