project-structure-audit

Auditing architectural conformance requires validating file, class, and interface existence against declared specifications. This skill checks contract surfaces and cross-system integration paths, emitting structured gap reports with severity levels and remediation tasks for deterministic development planning.

Architectural conformance checking validates that contract surfaces like methods and resources align with specification documents. You need it before starting development sprints to identify missing components or integration points that could cause runtime errors or delays.

Validating cross-system integration paths involves checking the existence of required interfaces and verifying connection integrity against declared requirements. This skill audits these boundaries and generates machine-readable gap reports detailing integration failures and required remediation tasks.

Yes, generating a deterministic, machine-readable gap report is the primary output of this audit process. It catalogs structural and conformance gaps with assigned severity levels and specific remediation tasks, ensuring outputs are directly usable for phased development planning.

Yes, this project structure audit operates without external dependencies. It independently validates project completeness, contract surfaces, and integration integrity using only declared requirement specifications and references to produce structured gap reports.

A project structure audit reports missing contract surfaces when implemented methods, signals, or resources do not align with the declared specification documents. The resulting gap report identifies these conformance failures and assigns severity and remediation tasks to correct them.