investigate

To check cross-spec dependencies, you investigate connection points between spec groups, atomic specs, and master specs to surface interface mismatches, environment variable inconsistencies, and API contract misalignments before writing any implementation code.

A spec investigation report is a structured document generated by analyzing connection points across specs to highlight critical, high, medium, and low integration risks including data shape conflicts and deployment assumption failures.

You need to run cross-spec contract alignment checks before master spec implementation, before one-off-spec implementation, and after requirements gathering to enforce API contract alignment and prevent integration bugs during later development.

You investigate environment variable naming conventions by running a scoped investigation command against single spec groups, cross-spec dependencies, or master specs to enforce interface consistency and identify naming mismatches across systems.

Yes, you can use spec investigation to identify deployment assumption risks by surfacing connection points between atomic specs and master specs, generating structured reports that prevent integration failures before implementation begins.

The best way to align API contracts is to run a structured cross-spec investigation that surfaces connection points between systems and components, enforcing interface consistency and generating risk reports to prevent integration bugs.