lid-coach

Identify and quantify drift between project artifacts and LID principles.

90|14|Updated Apr 11, 2026

Search Tags:#governance #review #lid #coach #advisory #hld #arrows

Ready to run

npx skills add https://github.com/jszmajda/lid --skill lid-coach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lid-coach
Source: https://github.com/jszmajda/lid/tree/main/plugins/linked-intent-dev/skills/lid-coach
Command: npx skills add https://github.com/jszmajda/lid --skill lid-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams evaluate how closely a project's HLD, LLDs, EARS specs, and related documentation align with LID principles, surfacing drift and providing a prioritized advisory plan to close gaps.

Core Features & Use Cases

Advisory, principle-level reviews that surface drift relative to LID principles and link findings to concrete actions.
Supports both fully configured LID projects and brownfield codebases, adapting the depth of review to scope.
Guidance on next steps, including reconciliation with /update-lid or arrow-maintenance checks, or clarifying questions to the team, without modifying code automatically.

Quick Start

Run /lid-coach on a configured project to receive an executive advisory report.

Frequently Asked Questions about lid-coach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my project documentation aligns with LID principles?▼

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.

What is the best way to review HLD and LLD drift in a brownfield codebase?▼

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.

Can I use an advisory review to find documentation scope and ownership issues?▼

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.

Does the LID advisory process automatically modify code to fix governance gaps?▼

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.

When do I need an executive advisory report for LID project alignment?▼

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.