test-derivation

Derive a TEST-SPEC.md from DomainSpec states.md without an LLM.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill test-derivation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-derivation
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/arcana/test-derivation
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill test-derivation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deterministically derive a test-obligation spec from a DomainSpec feature's aspect docs without using an LLM.

Core Features & Use Cases

  • Deterministic, content-addressed generation of test obligations from DomainSpec aspect docs.
  • Round-trip oracle verification that ensures engine-derived obligations superset committed obligations.
  • End-to-end L0 derivation flow with auditable provenance and stable keys.

Quick Start

Run the L0 derive tool on your DomainSpec states.md to produce TEST-SPEC.md and validate it with the round-trip oracle.

Frequently Asked Questions about test-derivation

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

FAQPage Schema
What is deterministic test-obligation derivation from DomainSpec docs?▼

Deterministic test-obligation derivation generates a TEST-SPEC.md from DomainSpec states.md without an LLM. It applies a round-trip oracle to verify engine obligations superset committed ones, ensuring end-to-end reproducibility and content-addressed stability.

How do I derive a test spec from a DomainSpec states.md file?▼

Run the L0 derivation tool on your DomainSpec states.md file to produce a TEST-SPEC.md. The tool deterministically processes aspect docs and applies a round-trip oracle to validate that engine obligations superset committed obligations with auditable provenance.

Do I need an LLM to generate test obligations from DomainSpec feature docs?▼

No, you do not need an LLM to generate test obligations from DomainSpec feature docs. The derivation process operates deterministically using a content-addressed key scheme and a stable engine contract to ensure end-to-end reproducibility without AI inference.

How does the round-trip oracle verify generated test obligations?▼

The round-trip oracle verifies generated test obligations by ensuring engine-derived obligations superset committed obligations in the TEST-SPEC.md. This mechanism enforces a stable engine contract and guarantees content-addressed keys remain auditable and reproducible.

What guarantees deterministic and reproducible test specs across derivation runs?▼

Deterministic and reproducible test specs are guaranteed by a content-addressed key scheme and a stable engine contract. The L0 derivation flow processes DomainSpec states.md without LLM variance, applying a round-trip oracle to ensure obligations remain stable and auditable.

What limitations exist when deriving test obligations from DomainSpec aspect docs?▼

A key limitation is that derivation strictly requires a DomainSpec states.md file to produce a TEST-SPEC.md. Because the process is deterministic and avoids LLMs, it cannot infer unstated obligations and relies entirely on explicit content within committed aspect docs.