vero-plan

Generate a translation plan for Lean 4 codebases into a .vero/plan.json file.

2|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/sunblaze-ucb/vero --skill vero-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vero-plan
Source: https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-plan
Command: npx skills add https://github.com/sunblaze-ucb/vero --skill vero-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vero-select, vero-source-{dafny,verus,coq}, vero-translate, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of a detailed translation plan for Lean 4 codebases, streamlining the process of converting code and specifications into Lean 4.

Core Features & Use Cases

  • Translation Plan Generation: Automatically generates a .vero/plan.json file containing a comprehensive plan for translating code and specifications.
  • API and Spec Mapping: Maps Lean 4 signatures to their corresponding API interfaces and specifications.
  • Use Case: After selecting a codebase with vero-select, this Skill can be used to create a translation plan that outlines the necessary steps for converting the code into Lean 4.

Quick Start

Use the vero-plan skill to generate a translation plan for the selected Lean 4 codebase.

Frequently Asked Questions about vero-plan

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

FAQPage Schema
How do I generate a translation plan for a Lean 4 codebase?

A translation plan for Lean 4 maps API signatures and specifications to outline the steps needed for converting source code into Lean 4. This Skill automates that mapping process to output a structured `.vero/plan.json` file.

What is specification mapping for Lean 4 code conversion?

Specification mapping for Lean 4 matches source code signatures to target API interfaces and specifications. This Skill automates the mapping to generate a comprehensive translation plan for the codebase.

Do I need to select a codebase before creating a Lean 4 translation plan?

Yes, you must select a codebase using `vero-select` before generating a translation plan. This Skill requires access to the selected source code files, specifications, and configuration files to map API signatures accurately.

Can I use vero-plan with Dafny, Verus, or Coq source files?

Yes, vero-plan works with Dafny, Verus, and Coq source files. It depends on the `vero-source-{dafny,verus,coq}` components to access these source formats and map their specifications into a Lean 4 translation plan.

What's the best way to automate translating code and specifications into Lean 4?

The best way to automate translating code and specifications into Lean 4 is to generate a detailed translation plan that maps API signatures and reference implementations. This provides a structured outline before executing the actual code conversion.

What files does the Lean 4 translation plan generation output?

The Lean 4 translation plan generation outputs a `.vero/plan.json` file. This file contains the comprehensive plan detailing the necessary steps for translating the mapped code and specifications into Lean 4.