issue/proof

Define acceptance criteria and proof plans for cnos issues with invariants, oracles, and surfaces.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill issue-proof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue/proof
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/issue/proof
Command: npx skills add https://github.com/usurobor/cnos --skill issue-proof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to designing and validating acceptance criteria and proof plans for issues in a cnos environment, ensuring decisions are verifiable and traceable.

Core Features & Use Cases

  • Formalizes acceptance criteria into independent, testable units with explicit invariants, oracles, and surface.
  • Produces a comprehensive proof plan that maps invariants, surfaces, and outcomes to operator-visible results.
  • Useful for complex issues where clear gating, negative cases, and known gaps are essential for robust validation.

Quick Start

State the issue, identify the invariant and oracle, and draft the accompanying acceptance criteria and proof plan.

Frequently Asked Questions about issue/proof

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

FAQPage Schema
How do I formalize acceptance criteria and a proof plan for an issue?

Acceptance criteria formalization requires defining independent, testable units with explicit invariants, oracles, and surfaces, ensuring decisions are verifiable and traceable for robust validation.

What is the best way to define invariants and oracles for testing?

Defining invariants and oracles involves producing a proof plan that maps invariants, surfaces, and outcomes to operator-visible results, outlining known gaps and ensuring clear gating for complex issues.

How do I structure test cases for positive, negative, and surface scenarios?

To structure test cases for positive, negative, and surface scenarios, formalize acceptance criteria into independent, testable units and outline known gaps to ensure robust validation across all outcomes.

When do I need a formal proof plan for issue verification?

You need a formal proof plan when precise testing and verification of closure are required, applying explicit structures for acceptance criteria to ensure decisions are verifiable and traceable.