workflow-equivalence-testing

Compare workflow shim and stategraph runtime states across Mode OFF and ON.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/transreal/claudecode --skill workflow-equivalence-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-equivalence-testing
Source: https://github.com/transreal/claudecode/tree/main/Claude%20Directives/skills/workflow-equivalence-testing
Command: npx skills add https://github.com/transreal/claudecode --skill workflow-equivalence-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confidently migrate or refactor workflow execution by determining whether a shim-based path behaves the same as the original stategraph implementation, instead of relying on fragile single-mode tests.

Core Features & Use Cases

  • Shim-equivalence test harness: Runs the workflow in Mode OFF and Mode ON and compares runtime state outputs to detect semantic differences.
  • Replay-based verification: Supports replaying held expressions and verification tests across both modes for outcome alignment.
  • Test-file result classification: Produces actionable buckets such as BothPass, OnlyOff, OnlyOn, and BothFail to identify where the shim or the legacy behavior diverges.
  • Mode-agnostic vs Mode-aware guidance: Distinguishes tests suited for cross-mode equivalence checks from those intended to validate mode-specific effects.

Quick Start

Ask the AI to run ClaudeOrchestratorWorkflowDiff`ClaudeStateGraphReplayTestFile on your existing test file in both modes, then summarize the resulting BothPass/OnlyOff/OnlyOn/BothFail counts so you know whether shim equivalence holds.

Frequently Asked Questions about workflow-equivalence-testing

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

FAQPage Schema
How do I verify semantic equivalence between a workflow shim and a stategraph implementation?

Semantic equivalence is verified by running the workflow in Mode OFF and Mode ON, then comparing runtime state outputs like status, stage keys, accumulators, and trace sequences to detect behavioral differences.

What is shim equivalence testing for workflow migrations?

Shim equivalence testing validates that a refactored shim execution path behaves identically to the original stategraph by replaying held expressions and verification tests across both modes for outcome alignment.

How do I debug mode-specific failures when enabling a workflow shim?

Debug mode-specific failures by running a diff harness in both modes to classify test results into BothPass, OnlyOff, OnlyOn, and BothFail buckets, pinpointing exactly where shim behavior diverges from legacy execution.

Can I design tests that work under both workflow shim True and False configurations?

Yes, you can design mode-aware tests by distinguishing tests suited for cross-mode equivalence checks from those validating mode-specific effects, ensuring deterministic result classification across both configurations.

What runtime state components are compared during stategraph and shim equivalence checks?

Equivalence checks perform structured comparisons of runtime status, state path, stage keys and types, accumulators, and trace sequence to classify deterministic results and detect semantic divergence between modes.

Do I need any external dependencies to run a workflow equivalence test harness?

No external dependencies are required to run the workflow equivalence test harness, as it operates by replaying held expressions and verification tests natively across both mode configurations to produce actionable result buckets.