validate

Execute runtime tests and generate a spec-compliance verification report.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill validate-lleontor705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/validate
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill validate-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that implementations meet specs by running runtime tests and collecting evidence, ensuring traceability from spec to deployment.

Core Features & Use Cases

  • Executes runtime tests against changes to collect evidence and generate a verification report.
  • Builds a Spec Compliance Matrix mapping each scenario to test results.
  • Persists the verification report to Cortex and returns the contract to the orchestrator.

Quick Start

Run the verification workflow on a completed change to generate and persist the verification report.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I verify code changes against specifications using runtime tests?

You can verify code changes against specifications by executing runtime tests that collect evidence and generate a formal verification report mapping each scenario to test results for traceability.

What is a spec compliance matrix and how does it validate implementation?

A spec compliance matrix validates implementation by mapping each specification scenario directly to its runtime test results, providing traceable evidence that the deployed code meets the documented requirements.

Can I use runtime verification for Cortex-based agent workflows and OpenSpec pipelines?

Yes, runtime verification applies to Cortex-based agent workflows and OpenSpec-enabled pipelines where artifacts like proposals, specs, designs, tasks, and apply-progress are available for validating changes.

What's the best way to automate end-to-end verification for code changes?

Automating end-to-end verification involves executing runtime tests, performing build checks, generating a spec-compliance matrix, issuing a verdict, and persisting the verification report under the designated change directory.

Do I need existing artifacts like proposals and tasks to generate a verification report?

Yes, you need existing artifacts such as proposal, spec, design, tasks, and apply-progress available within your OpenSpec-enabled pipeline to execute the verification and generate the formal report.

Where does the verification report persist after running runtime tests on a change?

The verification report persists under the sdd/{change-name}/verify-report directory, ensuring the formal verification output and spec-compliance matrix remain accessible for the orchestrator.