bidirectional-differential

Audits EARS-to-code mappings by comparing reconstructed EARS from code with original requirements.

Updated Apr 26, 2026

Search Tags:#code analysis #audit #EARS #requirement mapping #coherence check

Ready to run

npx skills add https://github.com/jmbeach/vat --skill bidirectional-differential-jmbeach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bidirectional-differential
Source: https://github.com/jmbeach/vat/tree/main/.claude/skills/bidirectional-differential
Command: npx skills add https://github.com/jmbeach/vat --skill bidirectional-differential-jmbeach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill audits the coherence between EARS (Easy Approach to Requirements Syntax) requirements and their corresponding code implementations, ensuring that both are aligned and accurately represent the intended system behavior.

Core Features & Use Cases

Bidirectional Audit: Compares the EARS requirements with the code implementations to check for drift and ensure consistency.
Parallel Sessions: Concurrently reconstructs the EARS from code and vice versa to uncover hidden requirements and unspoken assumptions.
Use Case: When a project is in a critical state, use this Skill to ensure that the code and EARS are in sync before proceeding to the next stage of development.

Quick Start

Run /differential-audit to initiate a bidirectional audit on the EARS requirements for your project.

Frequently Asked Questions about bidirectional-differential

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

FAQPage Schema

How do I check for drift between EARS requirements and code implementations?▼

To check for drift between EARS requirements and code, you conduct a bidirectional audit comparing reconstructed EARS from code against the original requirements to ensure consistency. This process uncovers hidden requirements and unspoken assumptions.

What is a bidirectional differential audit for requirement mapping?▼

A bidirectional differential audit for requirement mapping concurrently reconstructs EARS syntax from existing code and vice versa, comparing both directions to verify coherence. It ensures that code and requirements accurately represent the intended system behavior.

How do I run a coherence check on EARS to code mappings?▼

You run a coherence check on EARS to code mappings by executing the `/differential-audit` command. This initiates parallel sessions that reconstruct requirements from the code and compare them against the original EARS specifications.

Does the EARS code audit require multiple Claude sessions to run?▼

Yes, the EARS code audit requires multiple Claude sessions to run. It uses concurrent parallel sessions to independently reconstruct EARS requirements from the code and vice versa before performing the final differential comparison.

When should I use a bidirectional audit for software requirements?▼

You should use a bidirectional audit for software requirements when a project is in a critical state and you need to ensure code and EARS are in sync. It verifies alignment before proceeding to the next stage of development.