adlc-architect-analyze

Analyze ADRs and AD to detect drift, gaps, and governance violations.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-architect-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adlc-architect-analyze
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-architect-analyze
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-architect-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze architecture documentation to identify inconsistencies, gaps, and quality issues between Architecture Decisions Records (ADRs) and the Architecture Description (AD). It provides a read-only assessment to prevent drift from creeping into the system design.

Core Features & Use Cases

  • ADR quality and completeness checks against MADR-style guidance.
  • Inter-ADR consistency analysis to surface conflicts, dependencies, and terminology drift.
  • ADR-to-AD drift detection to reveal decisions not reflected in AD.md.
  • AD-to-ADR drift checks to surface gaps where AD descriptions lack supporting ADRs.
  • Staleness and placeholder detection to keep artifacts current.

Quick Start

Audit ADRs and AD to surface drift, then generate a read-only report of findings.

Frequently Asked Questions about adlc-architect-analyze

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

FAQPage Schema
How do I detect drift between ADRs and Architecture Description documents?

Detect ADR-to-AD drift by analyzing architecture documentation to surface decisions not reflected in AD.md, and report gaps without modifying files. It provides read-only assessment to prevent inconsistencies from creeping into system design.

What is architecture drift detection in software engineering?

Architecture drift detection identifies mismatches, conflicts, and quality gaps between Architecture Decision Records and Architecture Descriptions across system artifacts. It surfaces terminology drift, missing decisions, and governance violations to keep artifacts current.

How do I check ADR quality and completeness against MADR guidance?

Check ADR quality by evaluating completeness against MADR-style guidance, analyzing inter-ADR consistency for conflicts and dependencies. The read-only audit identifies staleness, placeholders, and terminology drift across system artifacts.

Can I analyze inter-ADR consistency without modifying my architecture files?

Yes, you can analyze inter-ADR consistency without modifying files because the assessment is strictly read-only. It surfaces conflicts, dependencies, and terminology drift across Architecture Decision Records while preserving original artifacts.

What's the best way to surface governance violations in architecture documentation?

Surface governance violations by applying consistency analysis across system and feature artifacts to detect drift, completeness gaps, and constitution alignment issues. It provides prioritized, actionable remediation guidance for identified violations.

Why does my Architecture Description lack supporting ADRs for certain decisions?

AD descriptions lack supporting ADRs due to documentation gaps where architectural decisions were made without formal records. AD-to-ADR drift checks surface these specific gaps to help prioritize remediation and improve governance.