bidirectional-differential

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.

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.

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.

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.

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.