solve

Apply a Z3-based solver to contract and state YAMLs for formal verification.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill solve-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solve
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/solve
Command: npx skills add https://github.com/michael-conrad/.opencode --skill solve-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formal verification of workflow constraints using a Z3-based solver to ensure that contract definitions and state data are internally consistent and comply with defined rules.

Core Features & Use Cases

  • Check preconditions and invariants against a given state, and validate postconditions.
  • Use subcommands: check, model, prove, and state to cover validation, querying, and theorem proving; plus a fallback path when Z3 is unavailable.
  • Provides a formal, auditable flow for pipeline governance and compliance, with explicit guidance on failure modes and counterexamples.

Quick Start

Load a contract.yaml and a state.yaml, then run the solver to validate constraints using the check subcommand

Frequently Asked Questions about solve

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

FAQPage Schema
How do I verify workflow constraints against a state YAML using Z3?

Formal verification of workflow constraints applies a Z3-based solver to contract and state YAMLs. It loads variables, asserts preconditions and invariants, and returns a satisfying model or UNSAT result with evidence.

What is the difference between the check, model, prove, and state tasks for contract validation?

Contract validation uses check to validate postconditions, model to query satisfying assignments, prove for theorem proving, and state to verify state data consistency against defined rules.

Can I validate pipeline governance and compliance rules without Z3 installed?

Pipeline governance and compliance validation includes a fallback pathway when Z3 is unavailable. This ensures constraint checking continues, though full theorem proving capabilities require the Z3 solver.

How do I formalize preconditions and invariants for workflow verification?

Workflow verification formalizes preconditions and invariants by defining them within a contract YAML. The solver loads these variables and asserts them against state data to check internal consistency.

What does an UNSAT result mean during state validation with a constraint solver?

An UNSAT result during state validation indicates the workflow constraints cannot be satisfied by the given state. The solver returns this result with explicit evidence and counterexamples for debugging.

Does the solve Skill work with standard YAML files for state and contract definitions?

The solve Skill works with contract YAML and state YAML files. It loads variables from these formats to assert preconditions and invariants for formal verification of workflow constraints.