cross-spec-validator

To catch cross-spec contradictions before build, validate coherence across multiple module specs using deterministic checks that detect naming drift and phantom references. This prevents globally inconsistent documentation from slipping through when each individual spec passes its own gate.

Cross-spec consistency validation detects contradictions, naming drift, and broken conventions across module specs. You need it during the SPEC stage when three or more module specs exist under the spec root, or immediately before the final spec gate preceding BUILD.

Check dependency graph acyclicity and event reentrancy across module specs by running six deterministic enforcement checks via a configurable YAML-driven validator. It outputs a consolidated JSON and markdown report enforcing FAIL, WARN, and SKIP status rules.

The spec validator works without a custom configuration file by applying bootstrap defaults and language auto-detection. You can optionally provide a .agents/cross-spec.config.yml file to customize language-aware patterns for your specific project.

The best way to fix reported spec inconsistencies is to follow the report-driven remediation loop. Review the consolidated JSON and markdown report, guide fixes until all checks pass, and then re-run the spec gate before proceeding to BUILD.

Six specific checks prevent global design drift in specs: singleton and global consistency, constant naming consistency, bitfield and enum consistency, event and callback reentrancy, coverage matrix integrity, and dependency graph acyclicity.