cross-module-check

Cross-module contract verification reads each module's CLAUDE.md integration section to map dependencies, then coordinates parallel verification agents across affected downstream modules to ensure compatibility after a shared interface is modified.

Cross-module contract verification is an automated process that reads CLAUDE.md integration maps to identify dependent modules, then dispatches parallel verification agents to execute integration tests and aggregate PASS/FAIL results with remediation guidance.

Yes, cross-module integration testing requires a CLAUDE.md file in each module to define the cross-module integration section, which the verification workflow reads to discover dependencies and identify downstream modules for parallel testing.

Automated dependency discovery reads the cross-module integration section in each module's CLAUDE.md to map downstream dependencies, identifies affected modules from code modifications, and builds a verification matrix to target parallel testing.

The best way to check if code changes break downstream module integrations is to run a verification orchestration workflow that reads CLAUDE.md dependency maps, dispatches parallel agents to test affected dependents, and aggregates PASS/FAIL statuses with remediation guidance.

When cross-module verification detects a failed integration test, the result aggregation phase collects the FAIL status and reports it with actionable remediation guidance to address the broken downstream module compatibility identified by the parallel verification agents.