lid-coach

To check LID principles alignment, you can review project artifacts like HLD, LLDs, and EARS specs to identify drift, quantify the gaps, and generate a prioritized advisory report with concrete next steps to close them.

Reviewing HLD and LLD drift in a brownfield codebase involves scanning existing governance artifacts and documentation scope to surface principle misalignments and ownership issues, adapting review depth to the project's current state.

Yes, an advisory review can find documentation scope and ownership issues by evaluating project artifacts against LID principles, generating a report that documents cascade issues and links findings to targeted questions for the team.

The LID advisory process does not automatically modify code; it generates a prioritized advisory report that suggests concrete next steps such as /update-lid reconciliations or targeted questions for the team to resolve governance gaps.

You need an executive advisory report for LID project alignment when you must identify and quantify drift between project artifacts and LID principles, providing a prioritized plan to close documentation gaps across configured or brownfield environments.