eval__design-proof-gates

Decompose value claims into falsifiable proof gates and eval-plans.

1|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill eval-design-proof-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval__design-proof-gates
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/eval__design-proof-gates
Command: npx skills add https://github.com/erikhazzard/vasir --skill eval-design-proof-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Eval Proof-Gate Designer helps teams convert vague product or engineering value claims into rigorously falsifiable gate-based contracts and learnable eval-plans, without implementing code or making premature commitments.

Core Features & Use Cases

  • Decomposes a value claim into required truths and corresponding gate classes
  • Generates compact eval-plan structure and missing-harness specs for upcoming work
  • Supports read-only discovery, orchestrated gates, and CI policy definition to guide safe product decisions

Quick Start

Provide a value-path claim and the skill will draft a durable eval-plan and gate design ready for implementation.

Frequently Asked Questions about eval__design-proof-gates

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

FAQPage Schema
How do I turn a product value claim into testable gates?

To turn a value claim into testable gates, you decompose the claim into required truths, select appropriate gate classes, and prescribe orchestrated validation runs to generate an eval-plan.

What is a falsifiable proof gate in software engineering?

A falsifiable proof gate is a structured contract that converts a vague value claim into rigorously testable conditions. It defines required truths and orchestrated runs to guide safe product decisions without premature code commitments.

How do I design an eval-plan for CI policy validation?

You design an eval-plan for CI policy validation by using read-only discovery to define gate classes and orchestrated runs. The output includes durable eval-plan structures and documented missing harnesses to guide implementation safely.

Can I use this approach to generate product code for my tests?

No, you cannot use this approach to generate product code. It explicitly avoids implementing product code and instead relies on read-only discovery to document missing harnesses and define CI policies for validation.

What is the best way to document missing harnesses for an eval-plan?

The best way to document missing harnesses is to generate compact eval-plan structures and missing-harness specs during gate design. This documents the required truths and validation artifacts needed for upcoming engineering work.