verify-constraints

Verify constraints from spec/constraints.yaml and generate verification reports.

37|5|Updated Nov 18, 2025

Search Tags:#verification #proofs #constraints #runtime-checks

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill verify-constraints

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-constraints
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/engineering-verify-constraints
Command: npx skills add https://github.com/BellaBe/lean-os --skill verify-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies constraints from spec, generating proofs for proof-obligation constraints and planning runtime checks for others.

Core Features & Use Cases

Load constraints.yaml and categorize proof_obligation
Lean proof verification for proven constraints
Runtime validation planning
Produce verification reports

Quick Start

Verify constraints from artifacts/v{N}/spec/constraints.yaml and produce a constraints report.

Frequently Asked Questions about verify-constraints

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

FAQPage Schema

How do I verify constraints against formal proofs and runtime checks?▼

Constraint verification loads your constraints.yaml, categorizes each by proof obligation, generates Lean proofs for provable constraints, and plans runtime validations for others. The Skill produces a verification report mapping each constraint to its proof status or planned runtime check.

What format should my constraints file use for verification?▼

Constraints are loaded from spec/constraints.yaml and categorized as invariants, preconditions, or postconditions. Each constraint tagged as a proof_obligation is verified through Lean proof checking; others are planned for runtime validation in your artifacts.

Can I verify constraints across multiple artifact versions?▼

Yes. The Skill applies verification across invariant, precondition, and postcondition categories in multiple artifacts and versions, generating versioned constraint reports to artifacts/v{N}/verify/constraints-report.yaml for each version processed.

What happens to constraints that can't be formally proven?▼

Constraints that fail Lean proof verification are classified as false obligations and moved into runtime validation planning. The verification report documents which constraints require runtime checks and how to implement them.

How do I interpret the constraints verification report?▼

The report maps each constraint to its verification outcome: proven constraints show their Lean proof status, while unproven constraints include planned runtime validation strategies. Reports are generated to artifacts/v{N}/verify/constraints-report.yaml for review and integration.