lean-specification

Plan Lean 4 theorem specifications with a three-part workflow.

2|Updated May 26, 2026
One-click install
npx skills add https://github.com/r-irbe/proof-skills --skill lean-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lean-specification
Source: https://github.com/r-irbe/proof-skills/tree/main/skills/lean-specification
Command: npx skills add https://github.com/r-irbe/proof-skills --skill lean-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and manage formal theorem specifications before implementation, ensuring clear requirements, design, and documentation.

Core Features & Use Cases

  • Structured three-part specification workflow (requirements, design, documentation) for Lean 4 proofs.
  • Lifecycle management and handoffs to relevant peers (e.g., proof, review, zettelkasten).
  • Centralized references and templates to accelerate project kickoff and consistency.

Quick Start

Create a new Lean theorem specification by filling in the three-part template and routing it to the appropriate teams.

Frequently Asked Questions about lean-specification

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

FAQPage Schema
How do I plan Lean 4 theorem specifications before implementation?

To plan Lean 4 theorem specifications before implementation, use a structured three-part workflow covering requirements, design, and documentation to ensure traceability and clear handoffs during proof development.

What is the best way to manage the lifecycle of Lean 4 proof specifications?

Managing the lifecycle of Lean 4 proof specifications involves tracking new theorems, lemmas, and definitions through a structured workflow with centralized templates, ensuring clear handoffs to relevant peers like proof and review teams.

Do I need a specification workflow for new Lean 4 tactics and definitions?

Yes, using a specification workflow for new Lean 4 tactics and definitions ensures structured design and traceability by enforcing requirements, design, and documentation phases before actual proof development begins.

How does a review council integrate with Lean 4 proof specifications?

A review council integrates with Lean 4 proof specifications by guiding proof development through the lifecycle management process, receiving structured handoffs from the three-part specification workflow to evaluate design and requirements.

Can I use centralized templates to accelerate Lean 4 theorem project kickoff?

Yes, you can use centralized templates to accelerate Lean 4 theorem project kickoff by providing consistent structures for requirements, design, and documentation, which streamlines the initial specification and routing process.

When should I not use a three-part specification workflow for Lean 4 proofs?

You might skip the three-part specification workflow for Lean 4 proofs when dealing with trivial lemmas that require no lifecycle management, peer handoffs, or formal design documentation, as the overhead would outweigh the benefits.